1
0
mirror of https://github.com/sjlongland/gentoo-docker-builder.git synced 2025-09-13 10:03:17 +10:00
Commit Graph

8 Commits

Author SHA1 Message Date
9a09edf5c4
README.md: update regarding move of project 2025-05-30 10:28:25 +10:00
e93b002279
mkimg-container.sh: Include portage tree in dev, exclude in rt.
In the development image, include the full portage tree, and any binary
packages and sources.

In the runtime image, exclude the portage tree and related files.  When
installing, we will use `--volumes-from` to mount those from a
development image container.
2017-05-21 17:45:58 +10:00
c7254f6d28
mkimg.sh: Ignore return value from docker rmi.
If `docker images` fails to find any dangling images, it returns no
values and `docker rmi` complains there's nothing to delete.  The
clean-up step failing is annoying rather than harmful.
2017-05-21 17:43:18 +10:00
4dbc9609fb
mkimg.sh: Declare /usr/portage and /var/lib/layman mountpoints.
This allows us to ship a "development" image that has all the binaries
and Portage tree embedded, and a "runtime" image without.

To install a package, we spin up the "development" image into a running
container and let it build any additional packages needed, then we can
spin up the runtime using `--volumes-from` pointing at the development
container before running `emerge -K` to install them.

After that is done, `docker commit` will commit that instance of the
runtime image to a new image which is our bundled package container.
2017-05-21 17:40:00 +10:00
f6f70471e9
mkimg-container: Set USE flags. 2017-04-23 10:43:19 +10:00
b49f303833
mkimg-container: Include portage tree and overlays
This does bloat the images out a bit, but:
- it removes one variable factor from builds, namely the host's portage
  tree
- in the runtime container, you'll only be storing it once
2017-04-23 10:41:54 +10:00
19979629b8
mkimg-container: Include util-linux in runtime. 2017-04-23 10:41:17 +10:00
2634253df3
Initial check-in 2017-04-23 08:02:51 +10:00