cisagov/guacscanner repository overview

⁠guacscanner-docker

⁠Docker Image

This project Dockerizes⁠ cisagov/guacscanner⁠, and the resulting Docker container is intended to run as a part of cisagov/guacamole-composition⁠, although it could - probably uselessly - run in a Docker composition⁠ alongside only the official PostgreSQL Docker image⁠.

⁠Running

⁠Running with Docker

To run the cisagov/guacscanner image via Docker:

docker run cisagov/guacscanner:1.3.0

⁠Running with Docker Compose

See cisagov/guacamole-composition⁠) for an example of how to create a compose.yml file to use Docker Compose⁠. With a compose.yml file in hand, one need only start the container and detach:

docker compose up --detach

⁠Using secrets with your container

This container also supports passing sensitive values via Docker secrets⁠. Passing sensitive values like your credentials can be more secure using secrets than using environment variables. See the secrets⁠ section below for a table of all supported secret files.

Again, see cisagov/guacamole-composition⁠) for an example of how to create a compose.yml file that uses Docker secrets.

⁠Updating your container

⁠Docker Compose

1. Pull the new image from Docker Hub:

   docker compose pull
   

   Copy

2. Recreate the running container by following the previous instructions⁠:

   docker compose up --detach
   

   Copy

⁠Docker

1. Stop the running container:

   docker stop <container_id>
   

   Copy

2. Pull the new image:

   docker pull cisagov/guacscanner:1.3.0
   

   Copy

3. Recreate and run the container by following the previous instructions⁠.

⁠Updating Python dependencies

This image uses Pipenv⁠ to manage Python dependencies using a Pipfile⁠. Both updating dependencies and changing the Pipenv⁠ configuration in src/Pipfile will result in a modified src/Pipfile.lock file that should be committed to the repository.

⁠Updating dependencies

If you want to update existing dependencies you would run the following command in the src/ subdirectory:

pipenv lock

⁠Modifying dependencies

If you want to add or remove dependencies you would update the src/Pipfile file and then update dependencies as you would above.

⁠Image tags

The images of this container are tagged with semantic versions⁠ of the underlying example project that they containerize. It is recommended that most users use a version tag (e.g. :1.3.0).

See the tags tab⁠ on Docker Hub for a list of all the supported tags.

⁠Volumes

There are no volumes.

⁠Ports

No ports are exposed by this container.

⁠Environment variables

⁠Required

There are no required environment variables.

⁠Optional

There are no optional environment variables.

⁠Secrets

⁠Building from source

Build the image locally using this git repository as the build context⁠:

docker build \
  --tag cisagov/guacscanner:1.3.0 \
  https://github.com/cisagov/guacscanner-docker.git#develop

⁠Cross-platform builds

To create images that are compatible with other platforms, you can use the buildx⁠ feature of Docker:

1. Copy the project to your machine using the Code button above or the command line:

   git clone https://github.com/cisagov/guacscanner-docker.git
   cd guacscanner-docker
   

   Copy

2. Create the Dockerfile-x file with buildx platform support:

   ./buildx-dockerfile.sh
   

   Copy

3. Build the image using buildx:

   docker buildx build \
     --file Dockerfile-x \
     --platform linux/amd64 \
     --output type=docker \
     --tag cisagov/guacscanner:1.3.0 .
   

   Copy

⁠Contributing

We welcome contributions! Please see CONTRIBUTING.md⁠ for details.

⁠License

This project is in the worldwide public domain⁠.

This project is in the public domain within the United States, and copyright and related rights in the work worldwide are waived through the CC0 1.0 Universal public domain dedication⁠.

All contributions to this project will be released under the CC0 dedication. By submitting a pull request, you are agreeing to comply with this waiver of copyright interest.