From f0da2ae046f9e1282bcbc92a68385cf83a7cb8a1 Mon Sep 17 00:00:00 2001 From: Stefan Tatschner Date: Fri, 19 Jul 2024 08:43:58 +0200 Subject: [PATCH 1/3] chore: Add Dockerfile --- Dockerfile | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 Dockerfile diff --git a/Dockerfile b/Dockerfile new file mode 100644 index 000000000..0e956a466 --- /dev/null +++ b/Dockerfile @@ -0,0 +1,15 @@ +# SPDX-FileCopyrightText: AISEC Pentesting Team +# +# SPDX-License-Identifier: CC0-1.0 + +FROM debian:stable + +LABEL org.opencontainers.image.authors="stefan.tatschner@aisec.fraunhofer.de" + +RUN DEBIAN_FRONTEND=noninteractive apt-get update && apt-get install -y python3 python3-poetry + +WORKDIR /app/gallia +COPY . . +RUN ["poetry", "install"] + +ENTRYPOINT [ "poetry", "run", "gallia" ] From c625b26f2f1039c678e1405216ef43b13222e19b Mon Sep 17 00:00:00 2001 From: Stefan Tatschner Date: Fri, 19 Jul 2024 08:52:27 +0200 Subject: [PATCH 2/3] chore: Add a CI for docker images --- .github/workflows/docker-publish.yml | 68 ++++++++++++++++++++++++++++ 1 file changed, 68 insertions(+) create mode 100644 .github/workflows/docker-publish.yml diff --git a/.github/workflows/docker-publish.yml b/.github/workflows/docker-publish.yml new file mode 100644 index 000000000..32d0ebd33 --- /dev/null +++ b/.github/workflows/docker-publish.yml @@ -0,0 +1,68 @@ +# SPDX-FileCopyrightText: AISEC Pentesting Team +# +# SPDX-License-Identifier: CC0-1.0 + +# https://docs.github.com/en/actions/publishing-packages/publishing-docker-images + + +name: Create and publish a Docker image + +on: + push: + branches: + - master + release: + types: [published] + pull_request: + +# Defines two custom environment variables for the workflow. These are used for the Container registry domain, and a name for the Docker image that this workflow builds. +env: + REGISTRY: ghcr.io + IMAGE_NAME: ${{ github.repository }} + +# There is a single job in this workflow. It's configured to run on the latest available version of Ubuntu. +jobs: + build-and-push-image: + runs-on: ubuntu-latest + # Sets the permissions granted to the `GITHUB_TOKEN` for the actions in this job. + permissions: + contents: read + packages: write + attestations: write + id-token: write + + steps: + - name: Checkout repository + uses: actions/checkout@v4 + # Uses the `docker/login-action` action to log in to the Container registry registry using the account and password that will publish the packages. Once published, the packages are scoped to the account defined here. + - name: Log in to the Container registry + uses: docker/login-action@65b78e6e13532edd9afa3aa52ac7964289d1a9c1 + with: + registry: ${{ env.REGISTRY }} + username: ${{ github.actor }} + password: ${{ secrets.GITHUB_TOKEN }} + # This step uses [docker/metadata-action](https://github.com/docker/metadata-action#about) to extract tags and labels that will be applied to the specified image. The `id` "meta" allows the output of this step to be referenced in a subsequent step. The `images` value provides the base name for the tags and labels. + - name: Extract metadata (tags, labels) for Docker + id: meta + uses: docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7 + with: + images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }} + # This step uses the `docker/build-push-action` action to build the image, based on your repository's `Dockerfile`. If the build succeeds, it pushes the image to GitHub Packages. + # It uses the `context` parameter to define the build's context as the set of files located in the specified path. For more information, see "[Usage](https://github.com/docker/build-push-action#usage)" in the README of the `docker/build-push-action` repository. + # It uses the `tags` and `labels` parameters to tag and label the image with the output from the "meta" step. + - name: Build and push Docker image + id: push + uses: docker/build-push-action@f2a1d5e99d037542a71f64918e516c093c6f3fc4 + with: + context: . + push: true + tags: ${{ steps.meta.outputs.tags }} + labels: ${{ steps.meta.outputs.labels }} + + # This step generates an artifact attestation for the image, which is an unforgeable statement about where and how it was built. It increases supply chain security for people who consume the image. For more information, see "[AUTOTITLE](/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds)." + - name: Generate artifact attestation + uses: actions/attest-build-provenance@v1 + with: + subject-name: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME}} + subject-digest: ${{ steps.push.outputs.digest }} + push-to-registry: true From 46020d348fe93ff6877f84f26beadd394b80bd31 Mon Sep 17 00:00:00 2001 From: Stefan Tatschner Date: Fri, 19 Jul 2024 09:10:31 +0200 Subject: [PATCH 3/3] docs: Mention Docker --- docs/setup.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/setup.md b/docs/setup.md index b37da840b..6e442d833 100644 --- a/docs/setup.md +++ b/docs/setup.md @@ -20,6 +20,10 @@ Python dependencies are listed in `pyproject.toml`. An overview of software repos where `gallia` is available is provided by [repology.org](https://repology.org/project/gallia/versions). +### Docker + +Docker images are published via the [Github Container registry](https://github.com/Fraunhofer-AISEC/gallia/pkgs/container/gallia). + ### Arch Linux ``` shell-session