Go to file
td5038 ee1a9e680c
Document new image types I added
Closes: https://github.com/gentoo/gentoo-docker-images/pull/124
Signed-off-by: John Helmert III <ajak@gentoo.org>
2023-11-26 12:53:44 -08:00
.github Add mergedusr support on amd64 2023-11-26 12:53:38 -08:00
.gitignore ignoring files not sent to final build 2015-03-11 23:34:52 +01:00
LICENSE add GPL-2 license wrt issue #4 thx to @wking 2014-06-23 10:40:48 +02:00
README.md Document new image types I added 2023-11-26 12:53:44 -08:00
build-python.sh add plumbing to produce a python testing image 2023-06-29 08:22:35 -07:00
build.sh generate containers for riscv64 (lp64 & lp64d one-level) 2021-10-21 13:13:13 +02:00
deploy.sh Fix arm64 stage3 builds 2022-04-12 08:04:02 +00:00
portage.Dockerfile Add CI builds for all supported stage3 architectures 2020-09-03 22:34:00 +02:00
python.Dockerfile add plumbing to produce a python testing image 2023-06-29 08:22:35 -07:00
stage3.Dockerfile Handle new clearsigned 'latest' files 2023-10-14 10:34:55 -07:00


Gentoo Docker Images


A collection of Dockerfiles for generating Gentoo docker images.

These images are intended to be created automatically by a cron job and pushed to docker hub. This repository include basic stage3 images and an image usable as a /var/db/repos/gentoo volume




The following targets are built and pushed to Docker Hub:

  • portage
  • stage3
    • amd64
      • stage3-amd64-hardened-nomultilib-openrc
      • stage3-amd64-hardened-openrc
      • stage3-amd64-musl
      • stage3-amd64-musl-hardened
      • stage3-amd64-nomultilib-openrc
      • stage3-amd64-nomultilib-systemd
      • stage3-amd64-openrc
      • stage3-amd64-desktop-openrc
      • stage3-amd64-systemd
      • stage3-amd64-systemd-mergedusr
      • stage3-amd64-desktop-systemd
      • stage3-amd64-desktop-systemd-mergedusr
    • arm
      • stage3-armv5tel-openrc
      • stage3-armv5tel-systemd
      • stage3-armv6j-openrc
      • stage3-armv6j-systemd
      • stage3-armv6j_hardfp-openrc
      • stage3-armv6j_hardfp-systemd
      • stage3-armv7a-openrc
      • stage3-armv7a-systemd
      • stage3-armv7a_hardfp_musl-openrc
      • stage3-armv7a_hardfp-openrc
      • stage3-armv7a_hardfp-systemd
    • arm64
      • stage3-arm64-desktop-openrc
      • stage3-arm64-desktop-systemd
      • stage3-arm64-musl
      • stage3-arm64-musl-hardened
      • stage3-arm64-openrc
      • stage3-arm64-systemd
    • ppc
      • stage3-ppc64le-musl-hardened-openrc
      • stage3-ppc64le-openrc
      • stage3-ppc64le-systemd
    • riscv
      • stage3-rv64_lp64-openrc
      • stage3-rv64_lp64-systemd
      • stage3-rv64_lp64d-openrc
      • stage3-rv64_lp64d-systemd
    • s390
      • stage3-s390x
    • x86
      • stage3-i686-hardened-openrc
      • stage3-i686-musl
      • stage3-i686-openrc
      • stage3-i686-systemd

The following upstream stage3 targets are not built at all:

[deprecated]: Deprecated stage3 target

[selinux]: SELinux doesn't seem to make sense inside containers

[under testing]: Not ready for container. Our arch team is working on testing it

[unsupported]: Unsupported Docker architecture

Building the containers

The containers are created using a multi-stage build, which requires Docker >= 19.03.0. The container being built is defined by the TARGET environment variable:

TARGET=stage3-amd64 ./build.sh

Using the portage container as a data volume

docker create -v /var/db/repos/gentoo --name myportagesnapshot gentoo/portage:latest /bin/true
docker run --interactive --tty --volumes-from myportagesnapshot gentoo/stage3:latest /bin/bash

Using the portage container in a multi-stage build

docker-17.05.0 or later supports multi-stage builds, allowing the portage volume to be used when creating images based on a stage3 image.

Example Dockerfile

# name the portage image
FROM gentoo/portage:latest as portage

# based on stage3 image
FROM gentoo/stage3:latest

# copy the entire portage volume in
COPY --from=portage /var/db/repos/gentoo /var/db/repos/gentoo

# continue with image build ...
RUN emerge -qv www-servers/apache # or whichever packages you need


We'd love to hear any ideas. Feel free to contact us via any of the following methods:


  • Use topic branches (i.e. foo) and fix branches (i.e. fix/foo) when submitting pull requests
  • Make meaningful commits ideally with the following form:
    • Subject linewhat this commit does
    • Blank line
    • Bodywhy this commit is necessary or desired
  • Pull requests should not include merge commits
  • Use amend and rebase to fix commits after a pull request has been submitted