Red Hat Universal Base Image (UBI) based images
Available versions:
- UBI 9: quay.io/devfile/base-developer-image:ubi9-latest
- UBI 10: quay.io/devfile/base-developer-image:ubi10-latest
Build with Docker buildkit:
UBI 9:
$ cd base/ubi9
$ DOCKER_BUILDKIT=1 docker image build --progress=plain -t quay.io/devfile/base-developer-image:ubi9-latest .UBI 10:
$ cd base/ubi10
$ DOCKER_BUILDKIT=1 docker image build --progress=plain -t quay.io/devfile/base-developer-image:ubi10-latest .Red Hat Universal Base Image (UBI) based image (quay.io/devfile/universal-developer-image:ubi9-latest)
Build with Docker buildkit:
$ cd universal/ubi9
$ DOCKER_BUILDKIT=1 docker image build --progress=plain -t quay.io/devfile/universal-developer-image:ubi9-latest .To build for a specific architecture:
UBI 9:
# amd64
$ DOCKER_BUILDKIT=1 docker image build --platform linux/amd64 --progress=plain -t quay.io/devfile/universal-developer-image:ubi9-latest .
# arm64
$ DOCKER_BUILDKIT=1 docker image build --platform linux/arm64 --progress=plain -t quay.io/devfile/universal-developer-image:ubi9-latest .UBI 10 Base Image:
# amd64
$ DOCKER_BUILDKIT=1 docker image build --platform linux/amd64 --progress=plain -t quay.io/devfile/base-developer-image:ubi10-latest .
# arm64
$ DOCKER_BUILDKIT=1 docker image build --platform linux/arm64 --progress=plain -t quay.io/devfile/base-developer-image:ubi10-latest .The build workflows support custom container registries through repository variables. This is useful for forks that want to publish to their own registry.
To configure:
- In your fork, go to Settings → Secrets and Variables → Actions → Variables
- Add a repository variable:
REGISTRY=your-registry.com/your-namespace - All workflows will automatically use your custom registry
Example: Setting REGISTRY to ghcr.io/youruser will publish images to:
ghcr.io/youruser/base-developer-image:ubi9-latestghcr.io/youruser/base-developer-image:ubi10-latestghcr.io/youruser/universal-developer-image:ubi9-latest