blob: 651b940f99bd0559332ef9746b7eaee5e3d0c652 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
|
# Gentoo Docker Images
[](https://github.com/gentoo/gentoo-docker-images/actions?workflow=build)
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](https://hub.docker.com/u/gentoo/).
This repository include basic stage3 images and an image usable as a `/usr/portage` volume
# DockerHub
https://hub.docker.com/u/gentoo/
## Inventory
The following targets are built and pushed to Docker Hub:
* `portage`
* `stage3`
* `amd64`
* `stage3-amd64`
* `stage3-amd64-hardened`
* `stage3-amd64-hardened-nomultilib`
* `stage3-amd64-musl-hardened`
* `stage3-amd64-musl-vanilla`
* `stage3-amd64-nomultilib`
* `stage3-amd64-systemd`
* `stage3-amd64-uclibc-hardened`
* `stage3-amd64-uclibc-vanilla`
* `arm64`
* `stage3-arm64`
* `stage3-arm64-systemd`
* `arm`
* `stage3-armv5tel`
* `stage3-armv6j_hardfp`
* `stage3-armv7a_hardfp`
* `ppc`
* `stage3-ppc64le`
* `s390`
* `stage3-s390x`
* `x86`
* `stage3-x86`
* `stage3-x86-hardened`
* `stage3-x86-musl-vanilla`
* `stage3-x86-systemd`
* `stage3-x86-uclibc-hardened`
* `stage3-x86-uclibc-vanilla`
The following upstream stage3 targets are not built at all (see [rationale](https://github.com/gentoo/gentoo-docker-images/issues/75#issuecomment-680776939)):
* `amd64`
* `stage3-amd64-hardened-selinux`
* `stage3-amd64-hardened-selinux+nomultilib`
* `stage3-x32`
* `arm`
* `stage3-armv4tl`
* `stage3-armv6j`
* `stage3-armv7a`
* `ppc`
* `stage3-ppc`
* `stage3-ppc64`
* `s390`
* `stage3-s390`
* `x86`
* `stage3-i486`
# 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 /usr/portage --name myportagesnapshot gentoo/portage:latest /bin/true
docker run --interactive --tty --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
# 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
```
# Contributing
We'd love to hear any ideas. Feel free to contact us via any of the following
methods:
* IRC: irc://freenode.net/#gentoo-containers
* EMAIL: gentoo-containers@lists.gentoo.org
* GITHUB: https://github.com/gentoo/gentoo-docker-images
## 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
|
GitWeb