Skip to content

Common effort to get an official and automated gentoo base docker container

License

Notifications You must be signed in to change notification settings

wuodan-docker/gentoo-docker-images

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Gentoo Docker Images

Build Status

A collection of Dockerfiles for generating Gentoo docker images.

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

DockerHub

https://hub.docker.com/u/gentoo/

Inventory

  • portage
  • stage3
    • stage3-amd64
      • stage3-amd64-hardened
      • stage3-amd64-nomultilib
      • stage3-amd64-hardened-nomultilib
    • stage3-x86
      • stage3-x86-hardened

Building the containers

The containers are created using a multi-stage build, which requires docker-17.05.0 or later. 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 /usr/portage --name myportagesnapshot gentoo/portage:latest /bin/true
docker run --volumes-from myportagesnapshot gentoo/stage3-amd64: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

# image is based on stage3-amd64
FROM gentoo/stage3-amd64:latest

# copy the entire portage volume in
COPY --from=portage /usr/portage /usr/portage

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

Contributing

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

Policy

  • 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 line–what this commit does
    • Blank line
    • Body–why 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

About

Common effort to get an official and automated gentoo base docker container

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Shell 100.0%