Skip to content

Docker container specifications which package dependencies for building Khronos documentation and software

License

Notifications You must be signed in to change notification settings

KhronosGroup/DockerContainers

Repository files navigation

DockerContainers

Docker container specifications which package dependencies for building Khronos documentation and software.

Images built from this github repository are pushed to the Dockerhub repository https://hub.docker.com/r/khronosgroup/docker-images.

Structure

Each Dockerfile is named <tag>.Dockerfile where <tag> (e.g. openxr, asciidoctor-spec) matches the tag for that image in the Dockerhub repository (e.g. KhronosGroup/docker-images:rust). A second tag is suffixed with .<date> representing a timestamp when this image was last modified.

Scripts

In general, any additional arguments are forwarded on to docker build except the first if it is "push", so this is how you can pass --no-cache to force a rebuild, etc.

  • Single-image scripts: pass a tag name as the first argument and a version as the second.
    • ./build-one.sh <tag> <date> - Just builds and tags the image locally, does not push to Dockerhub. Use for testing modifications.
    • ./build-one.sh <tag> <date> push - Builds and tags the image locally, then pushes it to Dockerhub. Only run this once you've committed (and ideally, pushed) the corresponding changes to this Git repo.
  • ./build-all.sh - Just calls ./build-one.sh on all the tags listed in it. Use as ./build-all.sh push to push all images to Dockerhub. If you add a new Dockerfile to this repo, add it to this script too.

Container Hashes

We have encountered problems with both gitlab and Github Actions CI not flushing cache when an updated image of the same name is pushed to dockerhub. While using different tags on every push is a possibility, another approach is to use the container SHA256 hash instead of the container name. This can be determined at container build time, or as follows:

$ docker inspect --format='{{index .RepoDigests 0}}' khronosgroup/docker-images:asciidoctor-spec
khronosgroup/docker-images@sha256:1535246a0270e5a118b11ba121ac3c08849782d27afcac28e3859424db659f2f

Using the last line as the image name in CI will pull that specific hash instead of whatever the currently cached version of the underlying image name is. This works in both gitlab and Github Actions.

About

Docker container specifications which package dependencies for building Khronos documentation and software

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published