This repository contains the Dockerfiles for the different Docker images that are pushed to the Github Container Registry (GHCR). They are visible in the Organizations "packages" tab and this repository's package tab.
When adding a new Docker container, please add a new Dockerfile to this repository. Make sure to include this line somewhere in the Dockerfile:
LABEL org.opencontainers.image.source https://github.com/steinwurf/build-imagesThis will allow GHCR to link the uploaded image with the Dockerfile.
You can follow this guide to authenticate with the GHCR.
Build the image and push it to the GHCR with a tag. Initially, this tag should be "latest"
docker build <IMAGE/PATH> -t ghcr.io/steinwurf/<IMAGE NAME>:latest
Once the image is built you can upload it to the GHCR using the following command:
docker push ghcr.io/steinwurf/<IMAGE NAME>:latest
Initially, the image will be private. To change this please find the packages in this repository and change the visibility to "public".
https://github.com/orgs/steinwurf/packages?repo_name=build-images
You can now test your container using the following command:
docker run -it ghcr.io/steinwurf/<IMAGE NAME>:latest
Once you have verified that everything works you can deploy a versioned image to the GHCR.
docker build <IMAGE/PATH> -t ghcr.io/steinwurf/<IMAGE NAME>:1.0.0 docker push ghcr.io/steinwurf/<IMAGE NAME>:1.0.0
Say you need a Docker image for 'foo' version 2, but the latest version on Github is 'foo' version 1. You can then create a 'foo-2' folder and a Dockerfile for the image.
If you are new to Dockerfiles, here are some resources to get you started:
To ensure that the package is visible in both this repo and the org, you have to add the following line somewhere in the Dockerfile:
LABEL org.opencontainers.image.source https://github.com/steinwurf/build-imagesIf you want to push the image to GHCR, login to the registry with your GitHub account from the command-line. You can follow this guide
After you have authenticated, you can build your image:
docker build /path/to/foo-2/ --tag ghcr.io/steinwurf/foo-2:latestMake sure that the container works as intended and finally push it to GHCR:
docker push ghcr.io/steinwurf/foo-2:latestIf your image works as intended after you have tested it for your use case, you can then build it and push it with the 1.0.0 tag. Versioned tags are assumed to work (unless they are very outdated) and the latest tag is used for testing in general.
Make sure to commit the 'foo-2' folder to this GitHub repository to keep the packages in sync with this repository.
By default when you add a new image, the package on the repo will be 'private'. Make sure to change its visibility to public in the specific package's settings on GitHub. If there are special circumstances where the package should not be public, find and ask someone capable of it.
We version our tools with semantic versioning. We separate the version of the package in the image from the version of the image. For example, if you add a new version 10 of clang, it would be called clang-10:1.0.0 in the above tag.
We choose not to use the latest tag for our GitHub Actions workflows, so there's no need to keep this up to date unless it is needed for your specific use case.