2016-09-28 01:42:05 +02:00
|
|
|
{
|
2019-06-27 20:15:42 +02:00
|
|
|
cacert,
|
|
|
|
callPackage,
|
|
|
|
closureInfo,
|
2016-09-28 01:42:05 +02:00
|
|
|
coreutils,
|
|
|
|
docker,
|
|
|
|
e2fsprogs,
|
|
|
|
findutils,
|
|
|
|
go,
|
2017-07-26 21:53:35 +02:00
|
|
|
jq,
|
2019-06-27 20:15:42 +02:00
|
|
|
jshon,
|
2016-09-28 01:42:05 +02:00
|
|
|
lib,
|
2019-06-27 20:15:42 +02:00
|
|
|
moreutils,
|
2018-10-01 09:51:52 +02:00
|
|
|
nix,
|
2019-06-27 20:15:42 +02:00
|
|
|
pigz,
|
|
|
|
referencesByPopularity,
|
2016-10-03 22:12:29 +02:00
|
|
|
rsync,
|
2019-06-27 20:15:42 +02:00
|
|
|
runCommand,
|
|
|
|
runtimeShell,
|
2016-09-28 01:42:05 +02:00
|
|
|
shadow,
|
2019-06-27 20:15:42 +02:00
|
|
|
skopeo,
|
|
|
|
stdenv,
|
2016-09-28 01:42:05 +02:00
|
|
|
storeDir ? builtins.storeDir,
|
2019-06-27 20:15:42 +02:00
|
|
|
substituteAll,
|
|
|
|
symlinkJoin,
|
2016-09-28 01:42:05 +02:00
|
|
|
utillinux,
|
|
|
|
vmTools,
|
|
|
|
writeReferencesToFile,
|
|
|
|
writeScript,
|
|
|
|
writeText,
|
|
|
|
}:
|
2015-11-19 13:11:17 +01:00
|
|
|
|
|
|
|
# WARNING: this API is unstable and may be subject to backwards-incompatible changes in the future.
|
2016-09-28 01:42:05 +02:00
|
|
|
|
2015-11-19 13:11:17 +01:00
|
|
|
rec {
|
|
|
|
|
2019-06-27 20:15:42 +02:00
|
|
|
examples = callPackage ./examples.nix {
|
|
|
|
inherit buildImage pullImage shadowSetup buildImageWithNixDb;
|
2016-10-03 19:07:33 +02:00
|
|
|
};
|
|
|
|
|
2018-05-06 04:38:47 +02:00
|
|
|
pullImage = let
|
|
|
|
fixName = name: builtins.replaceStrings ["/" ":"] ["-" "-"] name;
|
|
|
|
in
|
|
|
|
{ imageName
|
2018-04-03 10:26:03 +02:00
|
|
|
# To find the digest of an image, you can use skopeo:
|
2018-06-13 02:56:13 +02:00
|
|
|
# see doc/functions.xml
|
2018-05-06 04:38:47 +02:00
|
|
|
, imageDigest
|
|
|
|
, sha256
|
2018-06-13 02:56:13 +02:00
|
|
|
, os ? "linux"
|
2018-09-19 08:13:15 +02:00
|
|
|
, arch ? "amd64"
|
2019-03-26 10:35:21 +01:00
|
|
|
|
|
|
|
# This is used to set name to the pulled image
|
|
|
|
, finalImageName ? imageName
|
2018-04-03 10:26:03 +02:00
|
|
|
# This used to set a tag to the pulled image
|
2018-05-06 04:38:47 +02:00
|
|
|
, finalImageTag ? "latest"
|
2019-03-26 10:35:21 +01:00
|
|
|
|
|
|
|
, name ? fixName "docker-image-${finalImageName}-${finalImageTag}.tar"
|
2018-05-06 04:38:47 +02:00
|
|
|
}:
|
|
|
|
|
|
|
|
runCommand name {
|
2019-03-26 10:35:21 +01:00
|
|
|
inherit imageDigest;
|
|
|
|
imageName = finalImageName;
|
2018-06-03 22:58:23 +02:00
|
|
|
imageTag = finalImageTag;
|
2019-06-27 20:15:42 +02:00
|
|
|
impureEnvVars = stdenv.lib.fetchers.proxyImpureEnvVars;
|
2018-05-06 04:38:47 +02:00
|
|
|
outputHashMode = "flat";
|
|
|
|
outputHashAlgo = "sha256";
|
|
|
|
outputHash = sha256;
|
|
|
|
|
2019-06-27 20:15:42 +02:00
|
|
|
nativeBuildInputs = lib.singleton skopeo;
|
|
|
|
SSL_CERT_FILE = "${cacert.out}/etc/ssl/certs/ca-bundle.crt";
|
2018-05-06 04:38:47 +02:00
|
|
|
|
|
|
|
sourceURL = "docker://${imageName}@${imageDigest}";
|
2019-03-26 10:35:21 +01:00
|
|
|
destNameTag = "${finalImageName}:${finalImageTag}";
|
2018-05-06 04:38:47 +02:00
|
|
|
} ''
|
2018-06-13 02:56:13 +02:00
|
|
|
skopeo --override-os ${os} --override-arch ${arch} copy "$sourceURL" "docker-archive://$out:$destNameTag"
|
2018-05-06 04:38:47 +02:00
|
|
|
'';
|
2016-09-28 01:42:05 +02:00
|
|
|
|
2015-11-19 13:11:17 +01:00
|
|
|
# We need to sum layer.tar, not a directory, hence tarsum instead of nix-hash.
|
|
|
|
# And we cannot untar it, because then we cannot preserve permissions ecc.
|
|
|
|
tarsum = runCommand "tarsum" {
|
2019-01-30 05:29:18 +01:00
|
|
|
nativeBuildInputs = [ go ];
|
2015-11-19 13:11:17 +01:00
|
|
|
} ''
|
|
|
|
mkdir tarsum
|
|
|
|
cd tarsum
|
|
|
|
|
|
|
|
cp ${./tarsum.go} tarsum.go
|
|
|
|
export GOPATH=$(pwd)
|
2019-03-05 19:53:21 +01:00
|
|
|
export GOCACHE="$TMPDIR/go-cache"
|
2018-03-26 18:47:31 +02:00
|
|
|
mkdir -p src/github.com/docker/docker/pkg
|
|
|
|
ln -sT ${docker.src}/components/engine/pkg/tarsum src/github.com/docker/docker/pkg/tarsum
|
2015-11-19 13:11:17 +01:00
|
|
|
go build
|
|
|
|
|
2018-09-25 19:54:45 +02:00
|
|
|
mkdir -p $out/bin
|
|
|
|
|
|
|
|
cp tarsum $out/bin/
|
2015-11-19 13:11:17 +01:00
|
|
|
'';
|
2016-09-28 01:42:05 +02:00
|
|
|
|
2015-11-19 13:11:17 +01:00
|
|
|
# buildEnv creates symlinks to dirs, which is hard to edit inside the overlay VM
|
2016-09-28 01:42:05 +02:00
|
|
|
mergeDrvs = {
|
|
|
|
derivations,
|
|
|
|
onlyDeps ? false
|
|
|
|
}:
|
2015-11-19 13:11:17 +01:00
|
|
|
runCommand "merge-drvs" {
|
2016-09-28 01:42:05 +02:00
|
|
|
inherit derivations onlyDeps;
|
2015-11-19 13:11:17 +01:00
|
|
|
} ''
|
2016-09-28 01:42:05 +02:00
|
|
|
if [[ -n "$onlyDeps" ]]; then
|
|
|
|
echo $derivations > $out
|
2015-11-19 13:11:17 +01:00
|
|
|
exit 0
|
|
|
|
fi
|
2016-09-28 01:42:05 +02:00
|
|
|
|
2015-11-19 13:11:17 +01:00
|
|
|
mkdir $out
|
2016-09-28 01:42:05 +02:00
|
|
|
for derivation in $derivations; do
|
|
|
|
echo "Merging $derivation..."
|
|
|
|
if [[ -d "$derivation" ]]; then
|
|
|
|
# If it's a directory, copy all of its contents into $out.
|
|
|
|
cp -drf --preserve=mode -f $derivation/* $out/
|
2015-11-19 13:11:17 +01:00
|
|
|
else
|
2016-09-28 01:42:05 +02:00
|
|
|
# Otherwise treat the derivation as a tarball and extract it
|
|
|
|
# into $out.
|
2015-11-19 13:11:17 +01:00
|
|
|
tar -C $out -xpf $drv || true
|
|
|
|
fi
|
|
|
|
done
|
|
|
|
'';
|
|
|
|
|
2016-09-28 01:42:05 +02:00
|
|
|
# Helper for setting up the base files for managing users and
|
|
|
|
# groups, only if such files don't exist already. It is suitable for
|
|
|
|
# being used in a runAsRoot script.
|
2015-11-19 13:11:17 +01:00
|
|
|
shadowSetup = ''
|
|
|
|
export PATH=${shadow}/bin:$PATH
|
|
|
|
mkdir -p /etc/pam.d
|
2016-09-28 01:42:05 +02:00
|
|
|
if [[ ! -f /etc/passwd ]]; then
|
2019-02-26 12:45:54 +01:00
|
|
|
echo "root:x:0:0::/root:${runtimeShell}" > /etc/passwd
|
2015-11-19 13:11:17 +01:00
|
|
|
echo "root:!x:::::::" > /etc/shadow
|
|
|
|
fi
|
2016-09-28 01:42:05 +02:00
|
|
|
if [[ ! -f /etc/group ]]; then
|
2015-11-19 13:11:17 +01:00
|
|
|
echo "root:x:0:" > /etc/group
|
|
|
|
echo "root:x::" > /etc/gshadow
|
|
|
|
fi
|
2016-09-28 01:42:05 +02:00
|
|
|
if [[ ! -f /etc/pam.d/other ]]; then
|
2015-11-19 13:11:17 +01:00
|
|
|
cat > /etc/pam.d/other <<EOF
|
2016-09-28 01:42:05 +02:00
|
|
|
account sufficient pam_unix.so
|
|
|
|
auth sufficient pam_rootok.so
|
|
|
|
password requisite pam_unix.so nullok sha512
|
|
|
|
session required pam_unix.so
|
|
|
|
EOF
|
2015-11-19 13:11:17 +01:00
|
|
|
fi
|
2016-09-28 01:42:05 +02:00
|
|
|
if [[ ! -f /etc/login.defs ]]; then
|
2015-11-19 13:11:17 +01:00
|
|
|
touch /etc/login.defs
|
|
|
|
fi
|
|
|
|
'';
|
|
|
|
|
2016-09-28 01:42:05 +02:00
|
|
|
# Run commands in a virtual machine.
|
|
|
|
runWithOverlay = {
|
|
|
|
name,
|
|
|
|
fromImage ? null,
|
|
|
|
fromImageName ? null,
|
|
|
|
fromImageTag ? null,
|
|
|
|
diskSize ? 1024,
|
|
|
|
preMount ? "",
|
|
|
|
postMount ? "",
|
|
|
|
postUmount ? ""
|
|
|
|
}:
|
2019-06-27 20:15:42 +02:00
|
|
|
let
|
|
|
|
result = vmTools.runInLinuxVM (
|
2015-11-19 13:11:17 +01:00
|
|
|
runCommand name {
|
2016-09-28 01:42:05 +02:00
|
|
|
preVM = vmTools.createEmptyImage {
|
|
|
|
size = diskSize;
|
|
|
|
fullName = "docker-run-disk";
|
|
|
|
};
|
2015-11-19 13:11:17 +01:00
|
|
|
inherit fromImage fromImageName fromImageTag;
|
2016-09-28 01:42:05 +02:00
|
|
|
|
2019-01-30 05:29:18 +01:00
|
|
|
nativeBuildInputs = [ utillinux e2fsprogs jshon rsync jq ];
|
2015-11-19 13:11:17 +01:00
|
|
|
} ''
|
|
|
|
mkdir disk
|
|
|
|
mkfs /dev/${vmTools.hd}
|
|
|
|
mount /dev/${vmTools.hd} disk
|
|
|
|
cd disk
|
|
|
|
|
2016-09-28 01:42:05 +02:00
|
|
|
if [[ -n "$fromImage" ]]; then
|
|
|
|
echo "Unpacking base image..."
|
2015-11-19 13:11:17 +01:00
|
|
|
mkdir image
|
|
|
|
tar -C image -xpf "$fromImage"
|
2017-09-28 12:56:23 +02:00
|
|
|
|
|
|
|
# If the image name isn't set, read it from the image repository json.
|
|
|
|
if [[ -z "$fromImageName" ]]; then
|
|
|
|
fromImageName=$(jshon -k < image/repositories | head -n 1)
|
|
|
|
echo "From-image name wasn't set. Read $fromImageName."
|
|
|
|
fi
|
|
|
|
|
|
|
|
# If the tag isn't set, use the name as an index into the json
|
|
|
|
# and read the first key found.
|
|
|
|
if [[ -z "$fromImageTag" ]]; then
|
|
|
|
fromImageTag=$(jshon -e $fromImageName -k < image/repositories \
|
|
|
|
| head -n1)
|
|
|
|
echo "From-image tag wasn't set. Read $fromImageTag."
|
|
|
|
fi
|
|
|
|
|
|
|
|
# Use the name and tag to get the parent ID field.
|
|
|
|
parentID=$(jshon -e $fromImageName -e $fromImageTag -u \
|
|
|
|
< image/repositories)
|
dockerTools.buildImage: support using a layered image in fromImage
Docker images used to be, essentially, a linked list of layers. Each
layer would have a tarball and a json document pointing to its parent,
and the image pointed to the top layer:
imageA ----> layerA
|
v
layerB
|
v
layerC
The current image spec changed this format to where the Image defined
the order and set of layers:
imageA ---> layerA
|--> layerB
`--> layerC
For backwards compatibility, docker produces images which follow both
specs: layers point to parents, and images also point to the entire
list:
imageA ---> layerA
| |
| v
|--> layerB
| |
| v
`--> layerC
This is nice for tooling which supported the older version and never
updated to support the newer format.
Our `buildImage` code only supported the old version, so in order for
`buildImage` to properly generate an image based on another image
with `fromImage`, the parent image's layers must fully support the old
mechanism.
This is not a problem in general, but is a problem with
`buildLayeredImage`.
`buildLayeredImage` creates images with newer image spec, because
individual store paths don't have a guaranteed parent layer. Including
a specific parent ID in the layer's json makes the output less likely
to cache hit when published or pulled.
This means until now, `buildLayeredImage` could not be the input to
`buildImage`.
The changes in this PR change `buildImage` to only use the layer's
manifest when locating parent IDs. This does break buildImage on
extremely old Docker images, though I do wonder how many of these
exist.
This work has been sponsored by Target.
2018-12-04 18:18:06 +01:00
|
|
|
|
|
|
|
cat ./image/manifest.json | jq -r '.[0].Layers | .[]' > layer-list
|
|
|
|
else
|
|
|
|
touch layer-list
|
2015-11-19 13:11:17 +01:00
|
|
|
fi
|
|
|
|
|
2017-09-28 12:56:23 +02:00
|
|
|
# Unpack all of the parent layers into the image.
|
2015-11-19 13:11:17 +01:00
|
|
|
lowerdir=""
|
dockerTools.buildImage: support using a layered image in fromImage
Docker images used to be, essentially, a linked list of layers. Each
layer would have a tarball and a json document pointing to its parent,
and the image pointed to the top layer:
imageA ----> layerA
|
v
layerB
|
v
layerC
The current image spec changed this format to where the Image defined
the order and set of layers:
imageA ---> layerA
|--> layerB
`--> layerC
For backwards compatibility, docker produces images which follow both
specs: layers point to parents, and images also point to the entire
list:
imageA ---> layerA
| |
| v
|--> layerB
| |
| v
`--> layerC
This is nice for tooling which supported the older version and never
updated to support the newer format.
Our `buildImage` code only supported the old version, so in order for
`buildImage` to properly generate an image based on another image
with `fromImage`, the parent image's layers must fully support the old
mechanism.
This is not a problem in general, but is a problem with
`buildLayeredImage`.
`buildLayeredImage` creates images with newer image spec, because
individual store paths don't have a guaranteed parent layer. Including
a specific parent ID in the layer's json makes the output less likely
to cache hit when published or pulled.
This means until now, `buildLayeredImage` could not be the input to
`buildImage`.
The changes in this PR change `buildImage` to only use the layer's
manifest when locating parent IDs. This does break buildImage on
extremely old Docker images, though I do wonder how many of these
exist.
This work has been sponsored by Target.
2018-12-04 18:18:06 +01:00
|
|
|
extractionID=0
|
2019-03-12 11:59:57 +01:00
|
|
|
for layerTar in $(tac layer-list); do
|
dockerTools.buildImage: support using a layered image in fromImage
Docker images used to be, essentially, a linked list of layers. Each
layer would have a tarball and a json document pointing to its parent,
and the image pointed to the top layer:
imageA ----> layerA
|
v
layerB
|
v
layerC
The current image spec changed this format to where the Image defined
the order and set of layers:
imageA ---> layerA
|--> layerB
`--> layerC
For backwards compatibility, docker produces images which follow both
specs: layers point to parents, and images also point to the entire
list:
imageA ---> layerA
| |
| v
|--> layerB
| |
| v
`--> layerC
This is nice for tooling which supported the older version and never
updated to support the newer format.
Our `buildImage` code only supported the old version, so in order for
`buildImage` to properly generate an image based on another image
with `fromImage`, the parent image's layers must fully support the old
mechanism.
This is not a problem in general, but is a problem with
`buildLayeredImage`.
`buildLayeredImage` creates images with newer image spec, because
individual store paths don't have a guaranteed parent layer. Including
a specific parent ID in the layer's json makes the output less likely
to cache hit when published or pulled.
This means until now, `buildLayeredImage` could not be the input to
`buildImage`.
The changes in this PR change `buildImage` to only use the layer's
manifest when locating parent IDs. This does break buildImage on
extremely old Docker images, though I do wonder how many of these
exist.
This work has been sponsored by Target.
2018-12-04 18:18:06 +01:00
|
|
|
echo "Unpacking layer $layerTar"
|
|
|
|
extractionID=$((extractionID + 1))
|
|
|
|
|
|
|
|
mkdir -p image/$extractionID/layer
|
2018-12-14 21:48:58 +01:00
|
|
|
tar -C image/$extractionID/layer -xpf image/$layerTar
|
|
|
|
rm image/$layerTar
|
2015-11-19 13:11:17 +01:00
|
|
|
|
dockerTools.buildImage: support using a layered image in fromImage
Docker images used to be, essentially, a linked list of layers. Each
layer would have a tarball and a json document pointing to its parent,
and the image pointed to the top layer:
imageA ----> layerA
|
v
layerB
|
v
layerC
The current image spec changed this format to where the Image defined
the order and set of layers:
imageA ---> layerA
|--> layerB
`--> layerC
For backwards compatibility, docker produces images which follow both
specs: layers point to parents, and images also point to the entire
list:
imageA ---> layerA
| |
| v
|--> layerB
| |
| v
`--> layerC
This is nice for tooling which supported the older version and never
updated to support the newer format.
Our `buildImage` code only supported the old version, so in order for
`buildImage` to properly generate an image based on another image
with `fromImage`, the parent image's layers must fully support the old
mechanism.
This is not a problem in general, but is a problem with
`buildLayeredImage`.
`buildLayeredImage` creates images with newer image spec, because
individual store paths don't have a guaranteed parent layer. Including
a specific parent ID in the layer's json makes the output less likely
to cache hit when published or pulled.
This means until now, `buildLayeredImage` could not be the input to
`buildImage`.
The changes in this PR change `buildImage` to only use the layer's
manifest when locating parent IDs. This does break buildImage on
extremely old Docker images, though I do wonder how many of these
exist.
This work has been sponsored by Target.
2018-12-04 18:18:06 +01:00
|
|
|
find image/$extractionID/layer -name ".wh.*" -exec bash -c 'name="$(basename {}|sed "s/^.wh.//")"; mknod "$(dirname {})/$name" c 0 0; rm {}' \;
|
2015-11-19 13:11:17 +01:00
|
|
|
|
2016-09-28 01:42:05 +02:00
|
|
|
# Get the next lower directory and continue the loop.
|
2019-04-30 08:42:24 +02:00
|
|
|
lowerdir=image/$extractionID/layer''${lowerdir:+:}$lowerdir
|
2015-11-19 13:11:17 +01:00
|
|
|
done
|
|
|
|
|
|
|
|
mkdir work
|
|
|
|
mkdir layer
|
|
|
|
mkdir mnt
|
|
|
|
|
2016-09-28 01:42:05 +02:00
|
|
|
${lib.optionalString (preMount != "") ''
|
|
|
|
# Execute pre-mount steps
|
|
|
|
echo "Executing pre-mount steps..."
|
|
|
|
${preMount}
|
|
|
|
''}
|
2015-11-19 13:11:17 +01:00
|
|
|
|
|
|
|
if [ -n "$lowerdir" ]; then
|
|
|
|
mount -t overlay overlay -olowerdir=$lowerdir,workdir=work,upperdir=layer mnt
|
|
|
|
else
|
|
|
|
mount --bind layer mnt
|
|
|
|
fi
|
|
|
|
|
2016-09-28 01:42:05 +02:00
|
|
|
${lib.optionalString (postMount != "") ''
|
|
|
|
# Execute post-mount steps
|
|
|
|
echo "Executing post-mount steps..."
|
|
|
|
${postMount}
|
|
|
|
''}
|
|
|
|
|
2015-11-19 13:11:17 +01:00
|
|
|
umount mnt
|
|
|
|
|
2016-09-28 01:42:05 +02:00
|
|
|
(
|
|
|
|
cd layer
|
|
|
|
cmd='name="$(basename {})"; touch "$(dirname {})/.wh.$name"; rm "{}"'
|
|
|
|
find . -type c -exec bash -c "$cmd" \;
|
|
|
|
)
|
2015-11-19 13:11:17 +01:00
|
|
|
|
|
|
|
${postUmount}
|
|
|
|
'');
|
2019-06-27 20:15:42 +02:00
|
|
|
in
|
|
|
|
runCommand name {} ''
|
|
|
|
mkdir -p $out
|
|
|
|
cd ${result}
|
|
|
|
cp layer.tar json VERSION $out
|
|
|
|
'';
|
2015-11-19 13:11:17 +01:00
|
|
|
|
|
|
|
exportImage = { name ? fromImage.name, fromImage, fromImageName ? null, fromImageTag ? null, diskSize ? 1024 }:
|
|
|
|
runWithOverlay {
|
|
|
|
inherit name fromImage fromImageName fromImageTag diskSize;
|
|
|
|
|
|
|
|
postMount = ''
|
2016-09-28 01:42:05 +02:00
|
|
|
echo "Packing raw image..."
|
2018-03-12 18:26:15 +01:00
|
|
|
tar -C mnt --hard-dereference --sort=name --mtime="@$SOURCE_DATE_EPOCH" -cf $out .
|
2015-11-19 13:11:17 +01:00
|
|
|
'';
|
|
|
|
};
|
2016-09-28 01:42:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
# Create an executable shell script which has the coreutils in its
|
|
|
|
# PATH. Since root scripts are executed in a blank environment, even
|
|
|
|
# things like `ls` or `echo` will be missing.
|
|
|
|
shellScript = name: text:
|
|
|
|
writeScript name ''
|
2019-02-26 12:45:54 +01:00
|
|
|
#!${runtimeShell}
|
2016-09-28 01:42:05 +02:00
|
|
|
set -e
|
|
|
|
export PATH=${coreutils}/bin:/bin
|
|
|
|
${text}
|
|
|
|
'';
|
|
|
|
|
dockerTools.buildLayeredImage: init
Create a many-layered Docker Image.
Implements much less than buildImage:
- Doesn't support specific uids/gids
- Doesn't support runninng commands after building
- Doesn't require qemu
- Doesn't create mutable copies of the files in the path
- Doesn't support parent images
If you want those feature, I recommend using buildLayeredImage as an
input to buildImage.
Notably, it does support:
- Caching low level, common paths based on a graph traversial
algorithm, see referencesByPopularity in
0a80233487993256e811f566b1c80a40394c03d6
- Configurable number of layers. If you're not using AUFS or not
extending the image, you can specify a larger number of layers at
build time:
pkgs.dockerTools.buildLayeredImage {
name = "hello";
maxLayers = 128;
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
- Parallelized creation of the layers, improving build speed.
- The contents of the image includes the closure of the configuration,
so you don't have to specify paths in contents and config.
With buildImage, paths referred to by the config were not included
automatically in the image. Thus, if you wanted to call Git, you
had to specify it twice:
pkgs.dockerTools.buildImage {
name = "hello";
contents = [ pkgs.gitFull ];
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
buildLayeredImage on the other hand includes the runtime closure of
the config when calculating the contents of the image:
pkgs.dockerTools.buildImage {
name = "hello";
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
Minor Problems
- If any of the store paths change, every layer will be rebuilt in
the nix-build. However, beacuse the layers are bit-for-bit
reproducable, when these images are loaded in to Docker they will
match existing layers and not be imported or uploaded twice.
Common Questions
- Aren't Docker layers ordered?
No. People who have used a Dockerfile before assume Docker's
Layers are inherently ordered. However, this is not true -- Docker
layers are content-addressable and are not explicitly layered until
they are composed in to an Image.
- What happens if I have more than maxLayers of store paths?
The first (maxLayers-2) most "popular" paths will have their own
individual layers, then layer #(maxLayers-1) will contain all the
remaining "unpopular" paths, and finally layer #(maxLayers) will
contain the Image configuration.
2018-09-25 16:53:42 +02:00
|
|
|
# Create $maxLayers worth of Docker Layers, one layer per store path
|
|
|
|
# unless there are more paths than $maxLayers. In that case, create
|
|
|
|
# $maxLayers-1 for the most popular layers, and smush the remainaing
|
|
|
|
# store paths in to one final layer.
|
|
|
|
mkManyPureLayers = {
|
|
|
|
name,
|
|
|
|
# Files to add to the layer.
|
|
|
|
closure,
|
|
|
|
configJson,
|
2019-08-13 01:59:40 +02:00
|
|
|
# Docker has a 125-layer maximum, we pick 100 to ensure there is
|
|
|
|
# plenty of room for extension.
|
|
|
|
# https://github.com/moby/moby/blob/b3e9f7b13b0f0c414fa6253e1f17a86b2cff68b5/layer/layer_store.go#L23-L26
|
|
|
|
maxLayers ? 100
|
dockerTools.buildLayeredImage: init
Create a many-layered Docker Image.
Implements much less than buildImage:
- Doesn't support specific uids/gids
- Doesn't support runninng commands after building
- Doesn't require qemu
- Doesn't create mutable copies of the files in the path
- Doesn't support parent images
If you want those feature, I recommend using buildLayeredImage as an
input to buildImage.
Notably, it does support:
- Caching low level, common paths based on a graph traversial
algorithm, see referencesByPopularity in
0a80233487993256e811f566b1c80a40394c03d6
- Configurable number of layers. If you're not using AUFS or not
extending the image, you can specify a larger number of layers at
build time:
pkgs.dockerTools.buildLayeredImage {
name = "hello";
maxLayers = 128;
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
- Parallelized creation of the layers, improving build speed.
- The contents of the image includes the closure of the configuration,
so you don't have to specify paths in contents and config.
With buildImage, paths referred to by the config were not included
automatically in the image. Thus, if you wanted to call Git, you
had to specify it twice:
pkgs.dockerTools.buildImage {
name = "hello";
contents = [ pkgs.gitFull ];
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
buildLayeredImage on the other hand includes the runtime closure of
the config when calculating the contents of the image:
pkgs.dockerTools.buildImage {
name = "hello";
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
Minor Problems
- If any of the store paths change, every layer will be rebuilt in
the nix-build. However, beacuse the layers are bit-for-bit
reproducable, when these images are loaded in to Docker they will
match existing layers and not be imported or uploaded twice.
Common Questions
- Aren't Docker layers ordered?
No. People who have used a Dockerfile before assume Docker's
Layers are inherently ordered. However, this is not true -- Docker
layers are content-addressable and are not explicitly layered until
they are composed in to an Image.
- What happens if I have more than maxLayers of store paths?
The first (maxLayers-2) most "popular" paths will have their own
individual layers, then layer #(maxLayers-1) will contain all the
remaining "unpopular" paths, and finally layer #(maxLayers) will
contain the Image configuration.
2018-09-25 16:53:42 +02:00
|
|
|
}:
|
2019-01-15 23:41:31 +01:00
|
|
|
let
|
|
|
|
storePathToLayer = substituteAll
|
2019-03-26 11:07:24 +01:00
|
|
|
{ shell = runtimeShell;
|
2019-02-21 15:10:45 +01:00
|
|
|
isExecutable = true;
|
2019-01-15 23:41:31 +01:00
|
|
|
src = ./store-path-to-layer.sh;
|
|
|
|
};
|
|
|
|
in
|
dockerTools.buildLayeredImage: init
Create a many-layered Docker Image.
Implements much less than buildImage:
- Doesn't support specific uids/gids
- Doesn't support runninng commands after building
- Doesn't require qemu
- Doesn't create mutable copies of the files in the path
- Doesn't support parent images
If you want those feature, I recommend using buildLayeredImage as an
input to buildImage.
Notably, it does support:
- Caching low level, common paths based on a graph traversial
algorithm, see referencesByPopularity in
0a80233487993256e811f566b1c80a40394c03d6
- Configurable number of layers. If you're not using AUFS or not
extending the image, you can specify a larger number of layers at
build time:
pkgs.dockerTools.buildLayeredImage {
name = "hello";
maxLayers = 128;
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
- Parallelized creation of the layers, improving build speed.
- The contents of the image includes the closure of the configuration,
so you don't have to specify paths in contents and config.
With buildImage, paths referred to by the config were not included
automatically in the image. Thus, if you wanted to call Git, you
had to specify it twice:
pkgs.dockerTools.buildImage {
name = "hello";
contents = [ pkgs.gitFull ];
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
buildLayeredImage on the other hand includes the runtime closure of
the config when calculating the contents of the image:
pkgs.dockerTools.buildImage {
name = "hello";
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
Minor Problems
- If any of the store paths change, every layer will be rebuilt in
the nix-build. However, beacuse the layers are bit-for-bit
reproducable, when these images are loaded in to Docker they will
match existing layers and not be imported or uploaded twice.
Common Questions
- Aren't Docker layers ordered?
No. People who have used a Dockerfile before assume Docker's
Layers are inherently ordered. However, this is not true -- Docker
layers are content-addressable and are not explicitly layered until
they are composed in to an Image.
- What happens if I have more than maxLayers of store paths?
The first (maxLayers-2) most "popular" paths will have their own
individual layers, then layer #(maxLayers-1) will contain all the
remaining "unpopular" paths, and finally layer #(maxLayers) will
contain the Image configuration.
2018-09-25 16:53:42 +02:00
|
|
|
runCommand "${name}-granular-docker-layers" {
|
|
|
|
inherit maxLayers;
|
|
|
|
paths = referencesByPopularity closure;
|
2019-01-30 05:29:18 +01:00
|
|
|
nativeBuildInputs = [ jshon rsync tarsum ];
|
dockerTools.buildLayeredImage: init
Create a many-layered Docker Image.
Implements much less than buildImage:
- Doesn't support specific uids/gids
- Doesn't support runninng commands after building
- Doesn't require qemu
- Doesn't create mutable copies of the files in the path
- Doesn't support parent images
If you want those feature, I recommend using buildLayeredImage as an
input to buildImage.
Notably, it does support:
- Caching low level, common paths based on a graph traversial
algorithm, see referencesByPopularity in
0a80233487993256e811f566b1c80a40394c03d6
- Configurable number of layers. If you're not using AUFS or not
extending the image, you can specify a larger number of layers at
build time:
pkgs.dockerTools.buildLayeredImage {
name = "hello";
maxLayers = 128;
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
- Parallelized creation of the layers, improving build speed.
- The contents of the image includes the closure of the configuration,
so you don't have to specify paths in contents and config.
With buildImage, paths referred to by the config were not included
automatically in the image. Thus, if you wanted to call Git, you
had to specify it twice:
pkgs.dockerTools.buildImage {
name = "hello";
contents = [ pkgs.gitFull ];
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
buildLayeredImage on the other hand includes the runtime closure of
the config when calculating the contents of the image:
pkgs.dockerTools.buildImage {
name = "hello";
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
Minor Problems
- If any of the store paths change, every layer will be rebuilt in
the nix-build. However, beacuse the layers are bit-for-bit
reproducable, when these images are loaded in to Docker they will
match existing layers and not be imported or uploaded twice.
Common Questions
- Aren't Docker layers ordered?
No. People who have used a Dockerfile before assume Docker's
Layers are inherently ordered. However, this is not true -- Docker
layers are content-addressable and are not explicitly layered until
they are composed in to an Image.
- What happens if I have more than maxLayers of store paths?
The first (maxLayers-2) most "popular" paths will have their own
individual layers, then layer #(maxLayers-1) will contain all the
remaining "unpopular" paths, and finally layer #(maxLayers) will
contain the Image configuration.
2018-09-25 16:53:42 +02:00
|
|
|
enableParallelBuilding = true;
|
|
|
|
}
|
|
|
|
''
|
|
|
|
# Delete impurities for store path layers, so they don't get
|
|
|
|
# shared and taint other projects.
|
|
|
|
cat ${configJson} \
|
|
|
|
| jshon -d config \
|
|
|
|
| jshon -s "1970-01-01T00:00:01Z" -i created > generic.json
|
|
|
|
|
|
|
|
# WARNING!
|
|
|
|
# The following code is fiddly w.r.t. ensuring every layer is
|
|
|
|
# created, and that no paths are missed. If you change the
|
|
|
|
# following head and tail call lines, double-check that your
|
|
|
|
# code behaves properly when the number of layers equals:
|
|
|
|
# maxLayers-1, maxLayers, and maxLayers+1
|
2019-01-15 23:41:31 +01:00
|
|
|
head -n $((maxLayers - 1)) $paths | cat -n | xargs -P$NIX_BUILD_CORES -n2 ${storePathToLayer}
|
dockerTools.buildLayeredImage: init
Create a many-layered Docker Image.
Implements much less than buildImage:
- Doesn't support specific uids/gids
- Doesn't support runninng commands after building
- Doesn't require qemu
- Doesn't create mutable copies of the files in the path
- Doesn't support parent images
If you want those feature, I recommend using buildLayeredImage as an
input to buildImage.
Notably, it does support:
- Caching low level, common paths based on a graph traversial
algorithm, see referencesByPopularity in
0a80233487993256e811f566b1c80a40394c03d6
- Configurable number of layers. If you're not using AUFS or not
extending the image, you can specify a larger number of layers at
build time:
pkgs.dockerTools.buildLayeredImage {
name = "hello";
maxLayers = 128;
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
- Parallelized creation of the layers, improving build speed.
- The contents of the image includes the closure of the configuration,
so you don't have to specify paths in contents and config.
With buildImage, paths referred to by the config were not included
automatically in the image. Thus, if you wanted to call Git, you
had to specify it twice:
pkgs.dockerTools.buildImage {
name = "hello";
contents = [ pkgs.gitFull ];
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
buildLayeredImage on the other hand includes the runtime closure of
the config when calculating the contents of the image:
pkgs.dockerTools.buildImage {
name = "hello";
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
Minor Problems
- If any of the store paths change, every layer will be rebuilt in
the nix-build. However, beacuse the layers are bit-for-bit
reproducable, when these images are loaded in to Docker they will
match existing layers and not be imported or uploaded twice.
Common Questions
- Aren't Docker layers ordered?
No. People who have used a Dockerfile before assume Docker's
Layers are inherently ordered. However, this is not true -- Docker
layers are content-addressable and are not explicitly layered until
they are composed in to an Image.
- What happens if I have more than maxLayers of store paths?
The first (maxLayers-2) most "popular" paths will have their own
individual layers, then layer #(maxLayers-1) will contain all the
remaining "unpopular" paths, and finally layer #(maxLayers) will
contain the Image configuration.
2018-09-25 16:53:42 +02:00
|
|
|
if [ $(cat $paths | wc -l) -ge $maxLayers ]; then
|
2019-01-15 23:41:31 +01:00
|
|
|
tail -n+$maxLayers $paths | xargs ${storePathToLayer} $maxLayers
|
dockerTools.buildLayeredImage: init
Create a many-layered Docker Image.
Implements much less than buildImage:
- Doesn't support specific uids/gids
- Doesn't support runninng commands after building
- Doesn't require qemu
- Doesn't create mutable copies of the files in the path
- Doesn't support parent images
If you want those feature, I recommend using buildLayeredImage as an
input to buildImage.
Notably, it does support:
- Caching low level, common paths based on a graph traversial
algorithm, see referencesByPopularity in
0a80233487993256e811f566b1c80a40394c03d6
- Configurable number of layers. If you're not using AUFS or not
extending the image, you can specify a larger number of layers at
build time:
pkgs.dockerTools.buildLayeredImage {
name = "hello";
maxLayers = 128;
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
- Parallelized creation of the layers, improving build speed.
- The contents of the image includes the closure of the configuration,
so you don't have to specify paths in contents and config.
With buildImage, paths referred to by the config were not included
automatically in the image. Thus, if you wanted to call Git, you
had to specify it twice:
pkgs.dockerTools.buildImage {
name = "hello";
contents = [ pkgs.gitFull ];
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
buildLayeredImage on the other hand includes the runtime closure of
the config when calculating the contents of the image:
pkgs.dockerTools.buildImage {
name = "hello";
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
Minor Problems
- If any of the store paths change, every layer will be rebuilt in
the nix-build. However, beacuse the layers are bit-for-bit
reproducable, when these images are loaded in to Docker they will
match existing layers and not be imported or uploaded twice.
Common Questions
- Aren't Docker layers ordered?
No. People who have used a Dockerfile before assume Docker's
Layers are inherently ordered. However, this is not true -- Docker
layers are content-addressable and are not explicitly layered until
they are composed in to an Image.
- What happens if I have more than maxLayers of store paths?
The first (maxLayers-2) most "popular" paths will have their own
individual layers, then layer #(maxLayers-1) will contain all the
remaining "unpopular" paths, and finally layer #(maxLayers) will
contain the Image configuration.
2018-09-25 16:53:42 +02:00
|
|
|
fi
|
|
|
|
|
|
|
|
echo "Finished building layer '$name'"
|
|
|
|
|
|
|
|
mv ./layers $out
|
|
|
|
'';
|
|
|
|
|
|
|
|
# Create a "Customisation" layer which adds symlinks at the root of
|
|
|
|
# the image to the root paths of the closure. Also add the config
|
|
|
|
# data like what command to run and the environment to run it in.
|
|
|
|
mkCustomisationLayer = {
|
|
|
|
name,
|
|
|
|
# Files to add to the layer.
|
|
|
|
contents,
|
|
|
|
baseJson,
|
2018-12-25 23:04:16 +01:00
|
|
|
extraCommands,
|
dockerTools.buildLayeredImage: init
Create a many-layered Docker Image.
Implements much less than buildImage:
- Doesn't support specific uids/gids
- Doesn't support runninng commands after building
- Doesn't require qemu
- Doesn't create mutable copies of the files in the path
- Doesn't support parent images
If you want those feature, I recommend using buildLayeredImage as an
input to buildImage.
Notably, it does support:
- Caching low level, common paths based on a graph traversial
algorithm, see referencesByPopularity in
0a80233487993256e811f566b1c80a40394c03d6
- Configurable number of layers. If you're not using AUFS or not
extending the image, you can specify a larger number of layers at
build time:
pkgs.dockerTools.buildLayeredImage {
name = "hello";
maxLayers = 128;
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
- Parallelized creation of the layers, improving build speed.
- The contents of the image includes the closure of the configuration,
so you don't have to specify paths in contents and config.
With buildImage, paths referred to by the config were not included
automatically in the image. Thus, if you wanted to call Git, you
had to specify it twice:
pkgs.dockerTools.buildImage {
name = "hello";
contents = [ pkgs.gitFull ];
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
buildLayeredImage on the other hand includes the runtime closure of
the config when calculating the contents of the image:
pkgs.dockerTools.buildImage {
name = "hello";
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
Minor Problems
- If any of the store paths change, every layer will be rebuilt in
the nix-build. However, beacuse the layers are bit-for-bit
reproducable, when these images are loaded in to Docker they will
match existing layers and not be imported or uploaded twice.
Common Questions
- Aren't Docker layers ordered?
No. People who have used a Dockerfile before assume Docker's
Layers are inherently ordered. However, this is not true -- Docker
layers are content-addressable and are not explicitly layered until
they are composed in to an Image.
- What happens if I have more than maxLayers of store paths?
The first (maxLayers-2) most "popular" paths will have their own
individual layers, then layer #(maxLayers-1) will contain all the
remaining "unpopular" paths, and finally layer #(maxLayers) will
contain the Image configuration.
2018-09-25 16:53:42 +02:00
|
|
|
uid ? 0, gid ? 0,
|
|
|
|
}:
|
|
|
|
runCommand "${name}-customisation-layer" {
|
2019-01-30 05:29:18 +01:00
|
|
|
nativeBuildInputs = [ jshon rsync tarsum ];
|
2018-12-25 23:04:16 +01:00
|
|
|
inherit extraCommands;
|
dockerTools.buildLayeredImage: init
Create a many-layered Docker Image.
Implements much less than buildImage:
- Doesn't support specific uids/gids
- Doesn't support runninng commands after building
- Doesn't require qemu
- Doesn't create mutable copies of the files in the path
- Doesn't support parent images
If you want those feature, I recommend using buildLayeredImage as an
input to buildImage.
Notably, it does support:
- Caching low level, common paths based on a graph traversial
algorithm, see referencesByPopularity in
0a80233487993256e811f566b1c80a40394c03d6
- Configurable number of layers. If you're not using AUFS or not
extending the image, you can specify a larger number of layers at
build time:
pkgs.dockerTools.buildLayeredImage {
name = "hello";
maxLayers = 128;
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
- Parallelized creation of the layers, improving build speed.
- The contents of the image includes the closure of the configuration,
so you don't have to specify paths in contents and config.
With buildImage, paths referred to by the config were not included
automatically in the image. Thus, if you wanted to call Git, you
had to specify it twice:
pkgs.dockerTools.buildImage {
name = "hello";
contents = [ pkgs.gitFull ];
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
buildLayeredImage on the other hand includes the runtime closure of
the config when calculating the contents of the image:
pkgs.dockerTools.buildImage {
name = "hello";
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
Minor Problems
- If any of the store paths change, every layer will be rebuilt in
the nix-build. However, beacuse the layers are bit-for-bit
reproducable, when these images are loaded in to Docker they will
match existing layers and not be imported or uploaded twice.
Common Questions
- Aren't Docker layers ordered?
No. People who have used a Dockerfile before assume Docker's
Layers are inherently ordered. However, this is not true -- Docker
layers are content-addressable and are not explicitly layered until
they are composed in to an Image.
- What happens if I have more than maxLayers of store paths?
The first (maxLayers-2) most "popular" paths will have their own
individual layers, then layer #(maxLayers-1) will contain all the
remaining "unpopular" paths, and finally layer #(maxLayers) will
contain the Image configuration.
2018-09-25 16:53:42 +02:00
|
|
|
}
|
|
|
|
''
|
|
|
|
cp -r ${contents}/ ./layer
|
|
|
|
|
2018-12-25 23:04:16 +01:00
|
|
|
if [[ -n $extraCommands ]]; then
|
|
|
|
chmod ug+w layer
|
|
|
|
(cd layer; eval "$extraCommands")
|
|
|
|
fi
|
|
|
|
|
dockerTools.buildLayeredImage: init
Create a many-layered Docker Image.
Implements much less than buildImage:
- Doesn't support specific uids/gids
- Doesn't support runninng commands after building
- Doesn't require qemu
- Doesn't create mutable copies of the files in the path
- Doesn't support parent images
If you want those feature, I recommend using buildLayeredImage as an
input to buildImage.
Notably, it does support:
- Caching low level, common paths based on a graph traversial
algorithm, see referencesByPopularity in
0a80233487993256e811f566b1c80a40394c03d6
- Configurable number of layers. If you're not using AUFS or not
extending the image, you can specify a larger number of layers at
build time:
pkgs.dockerTools.buildLayeredImage {
name = "hello";
maxLayers = 128;
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
- Parallelized creation of the layers, improving build speed.
- The contents of the image includes the closure of the configuration,
so you don't have to specify paths in contents and config.
With buildImage, paths referred to by the config were not included
automatically in the image. Thus, if you wanted to call Git, you
had to specify it twice:
pkgs.dockerTools.buildImage {
name = "hello";
contents = [ pkgs.gitFull ];
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
buildLayeredImage on the other hand includes the runtime closure of
the config when calculating the contents of the image:
pkgs.dockerTools.buildImage {
name = "hello";
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
Minor Problems
- If any of the store paths change, every layer will be rebuilt in
the nix-build. However, beacuse the layers are bit-for-bit
reproducable, when these images are loaded in to Docker they will
match existing layers and not be imported or uploaded twice.
Common Questions
- Aren't Docker layers ordered?
No. People who have used a Dockerfile before assume Docker's
Layers are inherently ordered. However, this is not true -- Docker
layers are content-addressable and are not explicitly layered until
they are composed in to an Image.
- What happens if I have more than maxLayers of store paths?
The first (maxLayers-2) most "popular" paths will have their own
individual layers, then layer #(maxLayers-1) will contain all the
remaining "unpopular" paths, and finally layer #(maxLayers) will
contain the Image configuration.
2018-09-25 16:53:42 +02:00
|
|
|
# Tar up the layer and throw it into 'layer.tar'.
|
|
|
|
echo "Packing layer..."
|
|
|
|
mkdir $out
|
2019-03-27 12:08:50 +01:00
|
|
|
tar --transform='s|^\./||' -C layer --sort=name --mtime="@$SOURCE_DATE_EPOCH" --owner=${toString uid} --group=${toString gid} -cf $out/layer.tar .
|
dockerTools.buildLayeredImage: init
Create a many-layered Docker Image.
Implements much less than buildImage:
- Doesn't support specific uids/gids
- Doesn't support runninng commands after building
- Doesn't require qemu
- Doesn't create mutable copies of the files in the path
- Doesn't support parent images
If you want those feature, I recommend using buildLayeredImage as an
input to buildImage.
Notably, it does support:
- Caching low level, common paths based on a graph traversial
algorithm, see referencesByPopularity in
0a80233487993256e811f566b1c80a40394c03d6
- Configurable number of layers. If you're not using AUFS or not
extending the image, you can specify a larger number of layers at
build time:
pkgs.dockerTools.buildLayeredImage {
name = "hello";
maxLayers = 128;
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
- Parallelized creation of the layers, improving build speed.
- The contents of the image includes the closure of the configuration,
so you don't have to specify paths in contents and config.
With buildImage, paths referred to by the config were not included
automatically in the image. Thus, if you wanted to call Git, you
had to specify it twice:
pkgs.dockerTools.buildImage {
name = "hello";
contents = [ pkgs.gitFull ];
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
buildLayeredImage on the other hand includes the runtime closure of
the config when calculating the contents of the image:
pkgs.dockerTools.buildImage {
name = "hello";
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
Minor Problems
- If any of the store paths change, every layer will be rebuilt in
the nix-build. However, beacuse the layers are bit-for-bit
reproducable, when these images are loaded in to Docker they will
match existing layers and not be imported or uploaded twice.
Common Questions
- Aren't Docker layers ordered?
No. People who have used a Dockerfile before assume Docker's
Layers are inherently ordered. However, this is not true -- Docker
layers are content-addressable and are not explicitly layered until
they are composed in to an Image.
- What happens if I have more than maxLayers of store paths?
The first (maxLayers-2) most "popular" paths will have their own
individual layers, then layer #(maxLayers-1) will contain all the
remaining "unpopular" paths, and finally layer #(maxLayers) will
contain the Image configuration.
2018-09-25 16:53:42 +02:00
|
|
|
|
|
|
|
# Compute a checksum of the tarball.
|
|
|
|
echo "Computing layer checksum..."
|
|
|
|
tarhash=$(tarsum < $out/layer.tar)
|
|
|
|
|
|
|
|
# Add a 'checksum' field to the JSON, with the value set to the
|
|
|
|
# checksum of the tarball.
|
|
|
|
cat ${baseJson} | jshon -s "$tarhash" -i checksum > $out/json
|
|
|
|
|
|
|
|
# Indicate to docker that we're using schema version 1.0.
|
|
|
|
echo -n "1.0" > $out/VERSION
|
|
|
|
'';
|
|
|
|
|
2016-09-28 01:42:05 +02:00
|
|
|
# Create a "layer" (set of files).
|
|
|
|
mkPureLayer = {
|
|
|
|
# Name of the layer
|
|
|
|
name,
|
|
|
|
# JSON containing configuration and metadata for this layer.
|
|
|
|
baseJson,
|
|
|
|
# Files to add to the layer.
|
|
|
|
contents ? null,
|
2017-04-23 15:45:21 +02:00
|
|
|
# When copying the contents into the image, preserve symlinks to
|
|
|
|
# directories (see `rsync -K`). Otherwise, transform those symlinks
|
|
|
|
# into directories.
|
|
|
|
keepContentsDirlinks ? false,
|
2016-09-28 01:42:05 +02:00
|
|
|
# Additional commands to run on the layer before it is tar'd up.
|
2017-07-01 13:23:12 +02:00
|
|
|
extraCommands ? "", uid ? 0, gid ? 0
|
2016-09-28 01:42:05 +02:00
|
|
|
}:
|
|
|
|
runCommand "docker-layer-${name}" {
|
2015-11-19 13:11:17 +01:00
|
|
|
inherit baseJson contents extraCommands;
|
2019-01-30 05:29:18 +01:00
|
|
|
nativeBuildInputs = [ jshon rsync tarsum ];
|
2016-09-28 01:42:05 +02:00
|
|
|
}
|
|
|
|
''
|
2015-11-19 13:11:17 +01:00
|
|
|
mkdir layer
|
2016-09-28 01:42:05 +02:00
|
|
|
if [[ -n "$contents" ]]; then
|
|
|
|
echo "Adding contents..."
|
|
|
|
for item in $contents; do
|
|
|
|
echo "Adding $item"
|
2017-04-23 15:45:21 +02:00
|
|
|
rsync -a${if keepContentsDirlinks then "K" else "k"} --chown=0:0 $item/ layer/
|
2015-11-19 13:11:17 +01:00
|
|
|
done
|
2016-09-28 01:42:05 +02:00
|
|
|
else
|
|
|
|
echo "No contents to add to layer."
|
|
|
|
fi
|
|
|
|
|
2017-07-01 16:59:15 +02:00
|
|
|
chmod ug+w layer
|
|
|
|
|
2016-09-28 01:42:05 +02:00
|
|
|
if [[ -n $extraCommands ]]; then
|
|
|
|
(cd layer; eval "$extraCommands")
|
2015-11-19 13:11:17 +01:00
|
|
|
fi
|
|
|
|
|
2016-09-28 01:42:05 +02:00
|
|
|
# Tar up the layer and throw it into 'layer.tar'.
|
|
|
|
echo "Packing layer..."
|
2015-11-19 13:11:17 +01:00
|
|
|
mkdir $out
|
2018-03-12 18:26:15 +01:00
|
|
|
tar -C layer --hard-dereference --sort=name --mtime="@$SOURCE_DATE_EPOCH" --owner=${toString uid} --group=${toString gid} -cf $out/layer.tar .
|
2016-09-28 01:42:05 +02:00
|
|
|
|
|
|
|
# Compute a checksum of the tarball.
|
|
|
|
echo "Computing layer checksum..."
|
2018-09-25 19:54:45 +02:00
|
|
|
tarhash=$(tarsum < $out/layer.tar)
|
2016-09-28 01:42:05 +02:00
|
|
|
|
|
|
|
# Add a 'checksum' field to the JSON, with the value set to the
|
|
|
|
# checksum of the tarball.
|
2018-09-25 19:54:45 +02:00
|
|
|
cat ${baseJson} | jshon -s "$tarhash" -i checksum > $out/json
|
2016-09-28 01:42:05 +02:00
|
|
|
|
|
|
|
# Indicate to docker that we're using schema version 1.0.
|
2015-11-19 13:11:17 +01:00
|
|
|
echo -n "1.0" > $out/VERSION
|
2016-09-28 01:42:05 +02:00
|
|
|
|
|
|
|
echo "Finished building layer '${name}'"
|
2015-11-19 13:11:17 +01:00
|
|
|
'';
|
|
|
|
|
2016-09-28 01:42:05 +02:00
|
|
|
# Make a "root" layer; required if we need to execute commands as a
|
|
|
|
# privileged user on the image. The commands themselves will be
|
|
|
|
# performed in a virtual machine sandbox.
|
|
|
|
mkRootLayer = {
|
|
|
|
# Name of the image.
|
|
|
|
name,
|
|
|
|
# Script to run as root. Bash.
|
|
|
|
runAsRoot,
|
|
|
|
# Files to add to the layer. If null, an empty layer will be created.
|
|
|
|
contents ? null,
|
2017-04-23 15:45:21 +02:00
|
|
|
# When copying the contents into the image, preserve symlinks to
|
|
|
|
# directories (see `rsync -K`). Otherwise, transform those symlinks
|
|
|
|
# into directories.
|
|
|
|
keepContentsDirlinks ? false,
|
2016-09-28 01:42:05 +02:00
|
|
|
# JSON containing configuration and metadata for this layer.
|
|
|
|
baseJson,
|
|
|
|
# Existing image onto which to append the new layer.
|
|
|
|
fromImage ? null,
|
|
|
|
# Name of the image we're appending onto.
|
|
|
|
fromImageName ? null,
|
|
|
|
# Tag of the image we're appending onto.
|
|
|
|
fromImageTag ? null,
|
|
|
|
# How much disk to allocate for the temporary virtual machine.
|
|
|
|
diskSize ? 1024,
|
|
|
|
# Commands (bash) to run on the layer; these do not require sudo.
|
|
|
|
extraCommands ? ""
|
|
|
|
}:
|
|
|
|
# Generate an executable script from the `runAsRoot` text.
|
2018-05-23 01:53:28 +02:00
|
|
|
let
|
|
|
|
runAsRootScript = shellScript "run-as-root.sh" runAsRoot;
|
|
|
|
extraCommandsScript = shellScript "extra-commands.sh" extraCommands;
|
2015-11-19 13:11:17 +01:00
|
|
|
in runWithOverlay {
|
2016-09-28 01:42:05 +02:00
|
|
|
name = "docker-layer-${name}";
|
|
|
|
|
2015-11-19 13:11:17 +01:00
|
|
|
inherit fromImage fromImageName fromImageTag diskSize;
|
|
|
|
|
2016-09-28 01:42:05 +02:00
|
|
|
preMount = lib.optionalString (contents != null && contents != []) ''
|
|
|
|
echo "Adding contents..."
|
|
|
|
for item in ${toString contents}; do
|
|
|
|
echo "Adding $item..."
|
2017-04-23 15:45:21 +02:00
|
|
|
rsync -a${if keepContentsDirlinks then "K" else "k"} --chown=0:0 $item/ layer/
|
2015-11-19 13:11:17 +01:00
|
|
|
done
|
2017-07-01 16:59:15 +02:00
|
|
|
|
|
|
|
chmod ug+w layer
|
2015-11-19 13:11:17 +01:00
|
|
|
'';
|
|
|
|
|
|
|
|
postMount = ''
|
2016-09-28 01:42:05 +02:00
|
|
|
mkdir -p mnt/{dev,proc,sys} mnt${storeDir}
|
|
|
|
|
|
|
|
# Mount /dev, /sys and the nix store as shared folders.
|
2015-11-19 13:11:17 +01:00
|
|
|
mount --rbind /dev mnt/dev
|
|
|
|
mount --rbind /sys mnt/sys
|
2016-09-28 01:42:05 +02:00
|
|
|
mount --rbind ${storeDir} mnt${storeDir}
|
2015-11-19 13:11:17 +01:00
|
|
|
|
2016-09-28 01:42:05 +02:00
|
|
|
# Execute the run as root script. See 'man unshare' for
|
|
|
|
# details on what's going on here; basically this command
|
|
|
|
# means that the runAsRootScript will be executed in a nearly
|
|
|
|
# completely isolated environment.
|
2015-11-19 13:11:17 +01:00
|
|
|
unshare -imnpuf --mount-proc chroot mnt ${runAsRootScript}
|
2016-09-28 01:42:05 +02:00
|
|
|
|
|
|
|
# Unmount directories and remove them.
|
|
|
|
umount -R mnt/dev mnt/sys mnt${storeDir}
|
|
|
|
rmdir --ignore-fail-on-non-empty \
|
|
|
|
mnt/dev mnt/proc mnt/sys mnt${storeDir} \
|
|
|
|
mnt$(dirname ${storeDir})
|
2015-11-19 13:11:17 +01:00
|
|
|
'';
|
2016-09-28 01:42:05 +02:00
|
|
|
|
2015-11-19 13:11:17 +01:00
|
|
|
postUmount = ''
|
2018-05-23 01:53:28 +02:00
|
|
|
(cd layer; ${extraCommandsScript})
|
2015-11-19 13:11:17 +01:00
|
|
|
|
2016-09-28 01:42:05 +02:00
|
|
|
echo "Packing layer..."
|
2019-06-27 20:15:42 +02:00
|
|
|
mkdir -p $out
|
2018-03-12 18:26:15 +01:00
|
|
|
tar -C layer --hard-dereference --sort=name --mtime="@$SOURCE_DATE_EPOCH" -cf $out/layer.tar .
|
2016-09-28 01:42:05 +02:00
|
|
|
|
|
|
|
# Compute the tar checksum and add it to the output json.
|
|
|
|
echo "Computing checksum..."
|
2018-09-25 19:54:45 +02:00
|
|
|
tarhash=$(${tarsum}/bin/tarsum < $out/layer.tar)
|
|
|
|
cat ${baseJson} | jshon -s "$tarhash" -i checksum > $out/json
|
2016-09-28 01:42:05 +02:00
|
|
|
# Indicate to docker that we're using schema version 1.0.
|
2015-11-19 13:11:17 +01:00
|
|
|
echo -n "1.0" > $out/VERSION
|
2016-09-28 01:42:05 +02:00
|
|
|
|
|
|
|
echo "Finished building layer '${name}'"
|
2015-11-19 13:11:17 +01:00
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
dockerTools.buildLayeredImage: init
Create a many-layered Docker Image.
Implements much less than buildImage:
- Doesn't support specific uids/gids
- Doesn't support runninng commands after building
- Doesn't require qemu
- Doesn't create mutable copies of the files in the path
- Doesn't support parent images
If you want those feature, I recommend using buildLayeredImage as an
input to buildImage.
Notably, it does support:
- Caching low level, common paths based on a graph traversial
algorithm, see referencesByPopularity in
0a80233487993256e811f566b1c80a40394c03d6
- Configurable number of layers. If you're not using AUFS or not
extending the image, you can specify a larger number of layers at
build time:
pkgs.dockerTools.buildLayeredImage {
name = "hello";
maxLayers = 128;
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
- Parallelized creation of the layers, improving build speed.
- The contents of the image includes the closure of the configuration,
so you don't have to specify paths in contents and config.
With buildImage, paths referred to by the config were not included
automatically in the image. Thus, if you wanted to call Git, you
had to specify it twice:
pkgs.dockerTools.buildImage {
name = "hello";
contents = [ pkgs.gitFull ];
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
buildLayeredImage on the other hand includes the runtime closure of
the config when calculating the contents of the image:
pkgs.dockerTools.buildImage {
name = "hello";
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
Minor Problems
- If any of the store paths change, every layer will be rebuilt in
the nix-build. However, beacuse the layers are bit-for-bit
reproducable, when these images are loaded in to Docker they will
match existing layers and not be imported or uploaded twice.
Common Questions
- Aren't Docker layers ordered?
No. People who have used a Dockerfile before assume Docker's
Layers are inherently ordered. However, this is not true -- Docker
layers are content-addressable and are not explicitly layered until
they are composed in to an Image.
- What happens if I have more than maxLayers of store paths?
The first (maxLayers-2) most "popular" paths will have their own
individual layers, then layer #(maxLayers-1) will contain all the
remaining "unpopular" paths, and finally layer #(maxLayers) will
contain the Image configuration.
2018-09-25 16:53:42 +02:00
|
|
|
buildLayeredImage = {
|
|
|
|
# Image Name
|
|
|
|
name,
|
|
|
|
# Image tag, the Nix's output hash will be used if null
|
|
|
|
tag ? null,
|
|
|
|
# Files to put on the image (a nix store path or list of paths).
|
|
|
|
contents ? [],
|
|
|
|
# Docker config; e.g. what command to run on the container.
|
|
|
|
config ? {},
|
|
|
|
# Time of creation of the image. Passing "now" will make the
|
|
|
|
# created date be the time of building.
|
|
|
|
created ? "1970-01-01T00:00:01Z",
|
2018-12-25 23:04:16 +01:00
|
|
|
# Optional bash script to run on the files prior to fixturizing the layer.
|
|
|
|
extraCommands ? "", uid ? 0, gid ? 0,
|
dockerTools.buildLayeredImage: init
Create a many-layered Docker Image.
Implements much less than buildImage:
- Doesn't support specific uids/gids
- Doesn't support runninng commands after building
- Doesn't require qemu
- Doesn't create mutable copies of the files in the path
- Doesn't support parent images
If you want those feature, I recommend using buildLayeredImage as an
input to buildImage.
Notably, it does support:
- Caching low level, common paths based on a graph traversial
algorithm, see referencesByPopularity in
0a80233487993256e811f566b1c80a40394c03d6
- Configurable number of layers. If you're not using AUFS or not
extending the image, you can specify a larger number of layers at
build time:
pkgs.dockerTools.buildLayeredImage {
name = "hello";
maxLayers = 128;
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
- Parallelized creation of the layers, improving build speed.
- The contents of the image includes the closure of the configuration,
so you don't have to specify paths in contents and config.
With buildImage, paths referred to by the config were not included
automatically in the image. Thus, if you wanted to call Git, you
had to specify it twice:
pkgs.dockerTools.buildImage {
name = "hello";
contents = [ pkgs.gitFull ];
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
buildLayeredImage on the other hand includes the runtime closure of
the config when calculating the contents of the image:
pkgs.dockerTools.buildImage {
name = "hello";
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
Minor Problems
- If any of the store paths change, every layer will be rebuilt in
the nix-build. However, beacuse the layers are bit-for-bit
reproducable, when these images are loaded in to Docker they will
match existing layers and not be imported or uploaded twice.
Common Questions
- Aren't Docker layers ordered?
No. People who have used a Dockerfile before assume Docker's
Layers are inherently ordered. However, this is not true -- Docker
layers are content-addressable and are not explicitly layered until
they are composed in to an Image.
- What happens if I have more than maxLayers of store paths?
The first (maxLayers-2) most "popular" paths will have their own
individual layers, then layer #(maxLayers-1) will contain all the
remaining "unpopular" paths, and finally layer #(maxLayers) will
contain the Image configuration.
2018-09-25 16:53:42 +02:00
|
|
|
# Docker's lowest maximum layer limit is 42-layers for an old
|
|
|
|
# version of the AUFS graph driver. We pick 24 to ensure there is
|
|
|
|
# plenty of room for extension. I believe the actual maximum is
|
|
|
|
# 128.
|
|
|
|
maxLayers ? 24
|
|
|
|
}:
|
|
|
|
let
|
|
|
|
baseName = baseNameOf name;
|
|
|
|
contentsEnv = symlinkJoin { name = "bulk-layers"; paths = (if builtins.isList contents then contents else [ contents ]); };
|
|
|
|
|
|
|
|
configJson = let
|
|
|
|
pure = writeText "${baseName}-config.json" (builtins.toJSON {
|
|
|
|
inherit created config;
|
|
|
|
architecture = "amd64";
|
|
|
|
os = "linux";
|
|
|
|
});
|
|
|
|
impure = runCommand "${baseName}-standard-dynamic-date.json"
|
2019-01-30 05:29:18 +01:00
|
|
|
{ nativeBuildInputs = [ jq ]; }
|
dockerTools.buildLayeredImage: init
Create a many-layered Docker Image.
Implements much less than buildImage:
- Doesn't support specific uids/gids
- Doesn't support runninng commands after building
- Doesn't require qemu
- Doesn't create mutable copies of the files in the path
- Doesn't support parent images
If you want those feature, I recommend using buildLayeredImage as an
input to buildImage.
Notably, it does support:
- Caching low level, common paths based on a graph traversial
algorithm, see referencesByPopularity in
0a80233487993256e811f566b1c80a40394c03d6
- Configurable number of layers. If you're not using AUFS or not
extending the image, you can specify a larger number of layers at
build time:
pkgs.dockerTools.buildLayeredImage {
name = "hello";
maxLayers = 128;
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
- Parallelized creation of the layers, improving build speed.
- The contents of the image includes the closure of the configuration,
so you don't have to specify paths in contents and config.
With buildImage, paths referred to by the config were not included
automatically in the image. Thus, if you wanted to call Git, you
had to specify it twice:
pkgs.dockerTools.buildImage {
name = "hello";
contents = [ pkgs.gitFull ];
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
buildLayeredImage on the other hand includes the runtime closure of
the config when calculating the contents of the image:
pkgs.dockerTools.buildImage {
name = "hello";
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
Minor Problems
- If any of the store paths change, every layer will be rebuilt in
the nix-build. However, beacuse the layers are bit-for-bit
reproducable, when these images are loaded in to Docker they will
match existing layers and not be imported or uploaded twice.
Common Questions
- Aren't Docker layers ordered?
No. People who have used a Dockerfile before assume Docker's
Layers are inherently ordered. However, this is not true -- Docker
layers are content-addressable and are not explicitly layered until
they are composed in to an Image.
- What happens if I have more than maxLayers of store paths?
The first (maxLayers-2) most "popular" paths will have their own
individual layers, then layer #(maxLayers-1) will contain all the
remaining "unpopular" paths, and finally layer #(maxLayers) will
contain the Image configuration.
2018-09-25 16:53:42 +02:00
|
|
|
''
|
|
|
|
jq ".created = \"$(TZ=utc date --iso-8601="seconds")\"" ${pure} > $out
|
|
|
|
'';
|
|
|
|
in if created == "now" then impure else pure;
|
|
|
|
|
|
|
|
bulkLayers = mkManyPureLayers {
|
|
|
|
name = baseName;
|
|
|
|
closure = writeText "closure" "${contentsEnv} ${configJson}";
|
|
|
|
# One layer will be taken up by the customisationLayer, so
|
|
|
|
# take up one less.
|
|
|
|
maxLayers = maxLayers - 1;
|
|
|
|
inherit configJson;
|
|
|
|
};
|
|
|
|
customisationLayer = mkCustomisationLayer {
|
|
|
|
name = baseName;
|
|
|
|
contents = contentsEnv;
|
|
|
|
baseJson = configJson;
|
2018-12-25 23:04:16 +01:00
|
|
|
inherit uid gid extraCommands;
|
dockerTools.buildLayeredImage: init
Create a many-layered Docker Image.
Implements much less than buildImage:
- Doesn't support specific uids/gids
- Doesn't support runninng commands after building
- Doesn't require qemu
- Doesn't create mutable copies of the files in the path
- Doesn't support parent images
If you want those feature, I recommend using buildLayeredImage as an
input to buildImage.
Notably, it does support:
- Caching low level, common paths based on a graph traversial
algorithm, see referencesByPopularity in
0a80233487993256e811f566b1c80a40394c03d6
- Configurable number of layers. If you're not using AUFS or not
extending the image, you can specify a larger number of layers at
build time:
pkgs.dockerTools.buildLayeredImage {
name = "hello";
maxLayers = 128;
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
- Parallelized creation of the layers, improving build speed.
- The contents of the image includes the closure of the configuration,
so you don't have to specify paths in contents and config.
With buildImage, paths referred to by the config were not included
automatically in the image. Thus, if you wanted to call Git, you
had to specify it twice:
pkgs.dockerTools.buildImage {
name = "hello";
contents = [ pkgs.gitFull ];
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
buildLayeredImage on the other hand includes the runtime closure of
the config when calculating the contents of the image:
pkgs.dockerTools.buildImage {
name = "hello";
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
Minor Problems
- If any of the store paths change, every layer will be rebuilt in
the nix-build. However, beacuse the layers are bit-for-bit
reproducable, when these images are loaded in to Docker they will
match existing layers and not be imported or uploaded twice.
Common Questions
- Aren't Docker layers ordered?
No. People who have used a Dockerfile before assume Docker's
Layers are inherently ordered. However, this is not true -- Docker
layers are content-addressable and are not explicitly layered until
they are composed in to an Image.
- What happens if I have more than maxLayers of store paths?
The first (maxLayers-2) most "popular" paths will have their own
individual layers, then layer #(maxLayers-1) will contain all the
remaining "unpopular" paths, and finally layer #(maxLayers) will
contain the Image configuration.
2018-09-25 16:53:42 +02:00
|
|
|
};
|
|
|
|
result = runCommand "docker-image-${baseName}.tar.gz" {
|
2019-01-30 05:29:18 +01:00
|
|
|
nativeBuildInputs = [ jshon pigz coreutils findutils jq ];
|
dockerTools.buildLayeredImage: init
Create a many-layered Docker Image.
Implements much less than buildImage:
- Doesn't support specific uids/gids
- Doesn't support runninng commands after building
- Doesn't require qemu
- Doesn't create mutable copies of the files in the path
- Doesn't support parent images
If you want those feature, I recommend using buildLayeredImage as an
input to buildImage.
Notably, it does support:
- Caching low level, common paths based on a graph traversial
algorithm, see referencesByPopularity in
0a80233487993256e811f566b1c80a40394c03d6
- Configurable number of layers. If you're not using AUFS or not
extending the image, you can specify a larger number of layers at
build time:
pkgs.dockerTools.buildLayeredImage {
name = "hello";
maxLayers = 128;
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
- Parallelized creation of the layers, improving build speed.
- The contents of the image includes the closure of the configuration,
so you don't have to specify paths in contents and config.
With buildImage, paths referred to by the config were not included
automatically in the image. Thus, if you wanted to call Git, you
had to specify it twice:
pkgs.dockerTools.buildImage {
name = "hello";
contents = [ pkgs.gitFull ];
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
buildLayeredImage on the other hand includes the runtime closure of
the config when calculating the contents of the image:
pkgs.dockerTools.buildImage {
name = "hello";
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
Minor Problems
- If any of the store paths change, every layer will be rebuilt in
the nix-build. However, beacuse the layers are bit-for-bit
reproducable, when these images are loaded in to Docker they will
match existing layers and not be imported or uploaded twice.
Common Questions
- Aren't Docker layers ordered?
No. People who have used a Dockerfile before assume Docker's
Layers are inherently ordered. However, this is not true -- Docker
layers are content-addressable and are not explicitly layered until
they are composed in to an Image.
- What happens if I have more than maxLayers of store paths?
The first (maxLayers-2) most "popular" paths will have their own
individual layers, then layer #(maxLayers-1) will contain all the
remaining "unpopular" paths, and finally layer #(maxLayers) will
contain the Image configuration.
2018-09-25 16:53:42 +02:00
|
|
|
# Image name and tag must be lowercase
|
|
|
|
imageName = lib.toLower name;
|
|
|
|
baseJson = configJson;
|
2019-01-16 13:47:16 +01:00
|
|
|
passthru.imageTag =
|
|
|
|
if tag == null
|
|
|
|
then lib.head (lib.splitString "-" (lib.last (lib.splitString "/" result)))
|
|
|
|
else lib.toLower tag;
|
dockerTools.buildLayeredImage: init
Create a many-layered Docker Image.
Implements much less than buildImage:
- Doesn't support specific uids/gids
- Doesn't support runninng commands after building
- Doesn't require qemu
- Doesn't create mutable copies of the files in the path
- Doesn't support parent images
If you want those feature, I recommend using buildLayeredImage as an
input to buildImage.
Notably, it does support:
- Caching low level, common paths based on a graph traversial
algorithm, see referencesByPopularity in
0a80233487993256e811f566b1c80a40394c03d6
- Configurable number of layers. If you're not using AUFS or not
extending the image, you can specify a larger number of layers at
build time:
pkgs.dockerTools.buildLayeredImage {
name = "hello";
maxLayers = 128;
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
- Parallelized creation of the layers, improving build speed.
- The contents of the image includes the closure of the configuration,
so you don't have to specify paths in contents and config.
With buildImage, paths referred to by the config were not included
automatically in the image. Thus, if you wanted to call Git, you
had to specify it twice:
pkgs.dockerTools.buildImage {
name = "hello";
contents = [ pkgs.gitFull ];
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
buildLayeredImage on the other hand includes the runtime closure of
the config when calculating the contents of the image:
pkgs.dockerTools.buildImage {
name = "hello";
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
Minor Problems
- If any of the store paths change, every layer will be rebuilt in
the nix-build. However, beacuse the layers are bit-for-bit
reproducable, when these images are loaded in to Docker they will
match existing layers and not be imported or uploaded twice.
Common Questions
- Aren't Docker layers ordered?
No. People who have used a Dockerfile before assume Docker's
Layers are inherently ordered. However, this is not true -- Docker
layers are content-addressable and are not explicitly layered until
they are composed in to an Image.
- What happens if I have more than maxLayers of store paths?
The first (maxLayers-2) most "popular" paths will have their own
individual layers, then layer #(maxLayers-1) will contain all the
remaining "unpopular" paths, and finally layer #(maxLayers) will
contain the Image configuration.
2018-09-25 16:53:42 +02:00
|
|
|
} ''
|
2019-01-16 13:47:16 +01:00
|
|
|
${if (tag == null) then ''
|
dockerTools.buildLayeredImage: init
Create a many-layered Docker Image.
Implements much less than buildImage:
- Doesn't support specific uids/gids
- Doesn't support runninng commands after building
- Doesn't require qemu
- Doesn't create mutable copies of the files in the path
- Doesn't support parent images
If you want those feature, I recommend using buildLayeredImage as an
input to buildImage.
Notably, it does support:
- Caching low level, common paths based on a graph traversial
algorithm, see referencesByPopularity in
0a80233487993256e811f566b1c80a40394c03d6
- Configurable number of layers. If you're not using AUFS or not
extending the image, you can specify a larger number of layers at
build time:
pkgs.dockerTools.buildLayeredImage {
name = "hello";
maxLayers = 128;
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
- Parallelized creation of the layers, improving build speed.
- The contents of the image includes the closure of the configuration,
so you don't have to specify paths in contents and config.
With buildImage, paths referred to by the config were not included
automatically in the image. Thus, if you wanted to call Git, you
had to specify it twice:
pkgs.dockerTools.buildImage {
name = "hello";
contents = [ pkgs.gitFull ];
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
buildLayeredImage on the other hand includes the runtime closure of
the config when calculating the contents of the image:
pkgs.dockerTools.buildImage {
name = "hello";
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
Minor Problems
- If any of the store paths change, every layer will be rebuilt in
the nix-build. However, beacuse the layers are bit-for-bit
reproducable, when these images are loaded in to Docker they will
match existing layers and not be imported or uploaded twice.
Common Questions
- Aren't Docker layers ordered?
No. People who have used a Dockerfile before assume Docker's
Layers are inherently ordered. However, this is not true -- Docker
layers are content-addressable and are not explicitly layered until
they are composed in to an Image.
- What happens if I have more than maxLayers of store paths?
The first (maxLayers-2) most "popular" paths will have their own
individual layers, then layer #(maxLayers-1) will contain all the
remaining "unpopular" paths, and finally layer #(maxLayers) will
contain the Image configuration.
2018-09-25 16:53:42 +02:00
|
|
|
outName="$(basename "$out")"
|
|
|
|
outHash=$(echo "$outName" | cut -d - -f 1)
|
|
|
|
|
|
|
|
imageTag=$outHash
|
2019-01-16 13:47:16 +01:00
|
|
|
'' else ''
|
|
|
|
imageTag="${tag}"
|
dockerTools.buildLayeredImage: init
Create a many-layered Docker Image.
Implements much less than buildImage:
- Doesn't support specific uids/gids
- Doesn't support runninng commands after building
- Doesn't require qemu
- Doesn't create mutable copies of the files in the path
- Doesn't support parent images
If you want those feature, I recommend using buildLayeredImage as an
input to buildImage.
Notably, it does support:
- Caching low level, common paths based on a graph traversial
algorithm, see referencesByPopularity in
0a80233487993256e811f566b1c80a40394c03d6
- Configurable number of layers. If you're not using AUFS or not
extending the image, you can specify a larger number of layers at
build time:
pkgs.dockerTools.buildLayeredImage {
name = "hello";
maxLayers = 128;
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
- Parallelized creation of the layers, improving build speed.
- The contents of the image includes the closure of the configuration,
so you don't have to specify paths in contents and config.
With buildImage, paths referred to by the config were not included
automatically in the image. Thus, if you wanted to call Git, you
had to specify it twice:
pkgs.dockerTools.buildImage {
name = "hello";
contents = [ pkgs.gitFull ];
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
buildLayeredImage on the other hand includes the runtime closure of
the config when calculating the contents of the image:
pkgs.dockerTools.buildImage {
name = "hello";
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
Minor Problems
- If any of the store paths change, every layer will be rebuilt in
the nix-build. However, beacuse the layers are bit-for-bit
reproducable, when these images are loaded in to Docker they will
match existing layers and not be imported or uploaded twice.
Common Questions
- Aren't Docker layers ordered?
No. People who have used a Dockerfile before assume Docker's
Layers are inherently ordered. However, this is not true -- Docker
layers are content-addressable and are not explicitly layered until
they are composed in to an Image.
- What happens if I have more than maxLayers of store paths?
The first (maxLayers-2) most "popular" paths will have their own
individual layers, then layer #(maxLayers-1) will contain all the
remaining "unpopular" paths, and finally layer #(maxLayers) will
contain the Image configuration.
2018-09-25 16:53:42 +02:00
|
|
|
''}
|
|
|
|
|
|
|
|
find ${bulkLayers} -mindepth 1 -maxdepth 1 | sort -t/ -k5 -n > layer-list
|
|
|
|
echo ${customisationLayer} >> layer-list
|
|
|
|
|
|
|
|
mkdir image
|
|
|
|
imageJson=$(cat ${configJson} | jq ". + {\"rootfs\": {\"diff_ids\": [], \"type\": \"layers\"}}")
|
|
|
|
manifestJson=$(jq -n "[{\"RepoTags\":[\"$imageName:$imageTag\"]}]")
|
|
|
|
for layer in $(cat layer-list); do
|
|
|
|
layerChecksum=$(sha256sum $layer/layer.tar | cut -d ' ' -f1)
|
|
|
|
layerID=$(sha256sum "$layer/json" | cut -d ' ' -f 1)
|
|
|
|
ln -s "$layer" "./image/$layerID"
|
|
|
|
|
2019-04-30 08:42:24 +02:00
|
|
|
manifestJson=$(echo "$manifestJson" | jq ".[0].Layers |= . + [\"$layerID/layer.tar\"]")
|
|
|
|
imageJson=$(echo "$imageJson" | jq ".history |= . + [{\"created\": \"$(jq -r .created ${configJson})\"}]")
|
|
|
|
imageJson=$(echo "$imageJson" | jq ".rootfs.diff_ids |= . + [\"sha256:$layerChecksum\"]")
|
dockerTools.buildLayeredImage: init
Create a many-layered Docker Image.
Implements much less than buildImage:
- Doesn't support specific uids/gids
- Doesn't support runninng commands after building
- Doesn't require qemu
- Doesn't create mutable copies of the files in the path
- Doesn't support parent images
If you want those feature, I recommend using buildLayeredImage as an
input to buildImage.
Notably, it does support:
- Caching low level, common paths based on a graph traversial
algorithm, see referencesByPopularity in
0a80233487993256e811f566b1c80a40394c03d6
- Configurable number of layers. If you're not using AUFS or not
extending the image, you can specify a larger number of layers at
build time:
pkgs.dockerTools.buildLayeredImage {
name = "hello";
maxLayers = 128;
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
- Parallelized creation of the layers, improving build speed.
- The contents of the image includes the closure of the configuration,
so you don't have to specify paths in contents and config.
With buildImage, paths referred to by the config were not included
automatically in the image. Thus, if you wanted to call Git, you
had to specify it twice:
pkgs.dockerTools.buildImage {
name = "hello";
contents = [ pkgs.gitFull ];
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
buildLayeredImage on the other hand includes the runtime closure of
the config when calculating the contents of the image:
pkgs.dockerTools.buildImage {
name = "hello";
config.Cmd = [ "${pkgs.gitFull}/bin/git" ];
};
Minor Problems
- If any of the store paths change, every layer will be rebuilt in
the nix-build. However, beacuse the layers are bit-for-bit
reproducable, when these images are loaded in to Docker they will
match existing layers and not be imported or uploaded twice.
Common Questions
- Aren't Docker layers ordered?
No. People who have used a Dockerfile before assume Docker's
Layers are inherently ordered. However, this is not true -- Docker
layers are content-addressable and are not explicitly layered until
they are composed in to an Image.
- What happens if I have more than maxLayers of store paths?
The first (maxLayers-2) most "popular" paths will have their own
individual layers, then layer #(maxLayers-1) will contain all the
remaining "unpopular" paths, and finally layer #(maxLayers) will
contain the Image configuration.
2018-09-25 16:53:42 +02:00
|
|
|
done
|
|
|
|
imageJsonChecksum=$(echo "$imageJson" | sha256sum | cut -d ' ' -f1)
|
|
|
|
echo "$imageJson" > "image/$imageJsonChecksum.json"
|
|
|
|
manifestJson=$(echo "$manifestJson" | jq ".[0].Config = \"$imageJsonChecksum.json\"")
|
|
|
|
echo "$manifestJson" > image/manifest.json
|
|
|
|
|
|
|
|
jshon -n object \
|
|
|
|
-n object -s "$layerID" -i "$imageTag" \
|
|
|
|
-i "$imageName" > image/repositories
|
|
|
|
|
|
|
|
echo "Cooking the image..."
|
|
|
|
tar -C image --dereference --hard-dereference --sort=name --mtime="@$SOURCE_DATE_EPOCH" --owner=0 --group=0 --mode=a-w --xform s:'^./':: -c . | pigz -nT > $out
|
|
|
|
|
|
|
|
echo "Finished."
|
|
|
|
'';
|
|
|
|
|
|
|
|
in
|
|
|
|
result;
|
|
|
|
|
2015-11-19 13:11:17 +01:00
|
|
|
# 1. extract the base image
|
|
|
|
# 2. create the layer
|
|
|
|
# 3. add layer deps to the layer itself, diffing with the base image
|
|
|
|
# 4. compute the layer id
|
|
|
|
# 5. put the layer in the image
|
|
|
|
# 6. repack the image
|
2016-09-28 01:42:05 +02:00
|
|
|
buildImage = args@{
|
|
|
|
# Image name.
|
|
|
|
name,
|
2018-06-29 19:20:55 +02:00
|
|
|
# Image tag, when null then the nix output hash will be used.
|
|
|
|
tag ? null,
|
2016-09-28 01:42:05 +02:00
|
|
|
# Parent image, to append to.
|
|
|
|
fromImage ? null,
|
|
|
|
# Name of the parent image; will be read from the image otherwise.
|
|
|
|
fromImageName ? null,
|
|
|
|
# Tag of the parent image; will be read from the image otherwise.
|
|
|
|
fromImageTag ? null,
|
|
|
|
# Files to put on the image (a nix store path or list of paths).
|
|
|
|
contents ? null,
|
2017-04-23 15:45:21 +02:00
|
|
|
# When copying the contents into the image, preserve symlinks to
|
|
|
|
# directories (see `rsync -K`). Otherwise, transform those symlinks
|
|
|
|
# into directories.
|
|
|
|
keepContentsDirlinks ? false,
|
2016-09-28 01:42:05 +02:00
|
|
|
# Docker config; e.g. what command to run on the container.
|
|
|
|
config ? null,
|
|
|
|
# Optional bash script to run on the files prior to fixturizing the layer.
|
2017-07-01 13:23:12 +02:00
|
|
|
extraCommands ? "", uid ? 0, gid ? 0,
|
2016-09-28 01:42:05 +02:00
|
|
|
# Optional bash script to run as root on the image when provisioning.
|
|
|
|
runAsRoot ? null,
|
|
|
|
# Size of the virtual machine disk to provision when building the image.
|
|
|
|
diskSize ? 1024,
|
2017-06-27 22:11:17 +02:00
|
|
|
# Time of creation of the image.
|
|
|
|
created ? "1970-01-01T00:00:01Z",
|
2016-09-28 01:42:05 +02:00
|
|
|
}:
|
2015-11-19 13:11:17 +01:00
|
|
|
|
|
|
|
let
|
2016-02-18 17:16:15 +01:00
|
|
|
baseName = baseNameOf name;
|
|
|
|
|
2016-09-28 01:42:05 +02:00
|
|
|
# Create a JSON blob of the configuration. Set the date to unix zero.
|
2018-09-20 17:40:36 +02:00
|
|
|
baseJson = let
|
|
|
|
pure = writeText "${baseName}-config.json" (builtins.toJSON {
|
|
|
|
inherit created config;
|
|
|
|
architecture = "amd64";
|
|
|
|
os = "linux";
|
|
|
|
});
|
|
|
|
impure = runCommand "${baseName}-config.json"
|
2019-01-30 05:29:18 +01:00
|
|
|
{ nativeBuildInputs = [ jq ]; }
|
2018-09-20 17:40:36 +02:00
|
|
|
''
|
|
|
|
jq ".created = \"$(TZ=utc date --iso-8601="seconds")\"" ${pure} > $out
|
|
|
|
'';
|
|
|
|
in if created == "now" then impure else pure;
|
2016-03-10 08:29:28 +01:00
|
|
|
|
2016-09-28 01:42:05 +02:00
|
|
|
layer =
|
|
|
|
if runAsRoot == null
|
2016-10-31 16:11:48 +01:00
|
|
|
then mkPureLayer {
|
|
|
|
name = baseName;
|
2017-11-03 15:53:00 +01:00
|
|
|
inherit baseJson contents keepContentsDirlinks extraCommands uid gid;
|
2016-10-31 16:11:48 +01:00
|
|
|
} else mkRootLayer {
|
|
|
|
name = baseName;
|
|
|
|
inherit baseJson fromImage fromImageName fromImageTag
|
2017-04-23 15:45:21 +02:00
|
|
|
contents keepContentsDirlinks runAsRoot diskSize
|
|
|
|
extraCommands;
|
2016-10-31 16:11:48 +01:00
|
|
|
};
|
2016-09-28 01:42:05 +02:00
|
|
|
result = runCommand "docker-image-${baseName}.tar.gz" {
|
2019-06-27 20:15:42 +02:00
|
|
|
nativeBuildInputs = [ jshon pigz coreutils findutils jq moreutils ];
|
2017-07-25 10:47:51 +02:00
|
|
|
# Image name and tag must be lowercase
|
|
|
|
imageName = lib.toLower name;
|
2018-06-29 19:20:55 +02:00
|
|
|
imageTag = if tag == null then "" else lib.toLower tag;
|
2015-11-19 13:11:17 +01:00
|
|
|
inherit fromImage baseJson;
|
2016-03-10 08:29:28 +01:00
|
|
|
layerClosure = writeReferencesToFile layer;
|
2016-09-28 01:42:05 +02:00
|
|
|
passthru.buildArgs = args;
|
|
|
|
passthru.layer = layer;
|
2015-11-19 13:11:17 +01:00
|
|
|
} ''
|
2018-06-29 19:20:55 +02:00
|
|
|
${lib.optionalString (tag == null) ''
|
|
|
|
outName="$(basename "$out")"
|
|
|
|
outHash=$(echo "$outName" | cut -d - -f 1)
|
|
|
|
|
|
|
|
imageTag=$outHash
|
|
|
|
''}
|
|
|
|
|
2016-09-23 23:10:47 +02:00
|
|
|
# Print tar contents:
|
|
|
|
# 1: Interpreted as relative to the root directory
|
|
|
|
# 2: With no trailing slashes on directories
|
2016-09-28 01:42:05 +02:00
|
|
|
# This is useful for ensuring that the output matches the
|
|
|
|
# values generated by the "find" command
|
2016-09-23 23:10:47 +02:00
|
|
|
ls_tar() {
|
2016-09-28 01:42:05 +02:00
|
|
|
for f in $(tar -tf $1 | xargs realpath -ms --relative-to=.); do
|
|
|
|
if [[ "$f" != "." ]]; then
|
|
|
|
echo "/$f"
|
|
|
|
fi
|
|
|
|
done
|
2016-09-23 23:10:47 +02:00
|
|
|
}
|
2016-09-28 01:42:05 +02:00
|
|
|
|
2015-11-19 13:11:17 +01:00
|
|
|
mkdir image
|
|
|
|
touch baseFiles
|
2016-09-28 01:42:05 +02:00
|
|
|
if [[ -n "$fromImage" ]]; then
|
|
|
|
echo "Unpacking base image..."
|
2015-11-19 13:11:17 +01:00
|
|
|
tar -C image -xpf "$fromImage"
|
dockerTools.buildImage: support using a layered image in fromImage
Docker images used to be, essentially, a linked list of layers. Each
layer would have a tarball and a json document pointing to its parent,
and the image pointed to the top layer:
imageA ----> layerA
|
v
layerB
|
v
layerC
The current image spec changed this format to where the Image defined
the order and set of layers:
imageA ---> layerA
|--> layerB
`--> layerC
For backwards compatibility, docker produces images which follow both
specs: layers point to parents, and images also point to the entire
list:
imageA ---> layerA
| |
| v
|--> layerB
| |
| v
`--> layerC
This is nice for tooling which supported the older version and never
updated to support the newer format.
Our `buildImage` code only supported the old version, so in order for
`buildImage` to properly generate an image based on another image
with `fromImage`, the parent image's layers must fully support the old
mechanism.
This is not a problem in general, but is a problem with
`buildLayeredImage`.
`buildLayeredImage` creates images with newer image spec, because
individual store paths don't have a guaranteed parent layer. Including
a specific parent ID in the layer's json makes the output less likely
to cache hit when published or pulled.
This means until now, `buildLayeredImage` could not be the input to
`buildImage`.
The changes in this PR change `buildImage` to only use the layer's
manifest when locating parent IDs. This does break buildImage on
extremely old Docker images, though I do wonder how many of these
exist.
This work has been sponsored by Target.
2018-12-04 18:18:06 +01:00
|
|
|
|
|
|
|
cat ./image/manifest.json | jq -r '.[0].Layers | .[]' > layer-list
|
|
|
|
|
2017-09-28 12:56:23 +02:00
|
|
|
# Do not import the base image configuration and manifest
|
|
|
|
chmod a+w image image/*.json
|
|
|
|
rm -f image/*.json
|
|
|
|
|
|
|
|
if [[ -z "$fromImageName" ]]; then
|
|
|
|
fromImageName=$(jshon -k < image/repositories|head -n1)
|
|
|
|
fi
|
|
|
|
if [[ -z "$fromImageTag" ]]; then
|
|
|
|
fromImageTag=$(jshon -e $fromImageName -k \
|
|
|
|
< image/repositories|head -n1)
|
|
|
|
fi
|
|
|
|
parentID=$(jshon -e $fromImageName -e $fromImageTag -u \
|
|
|
|
< image/repositories)
|
|
|
|
|
|
|
|
for l in image/*/layer.tar; do
|
|
|
|
ls_tar $l >> baseFiles
|
2015-11-19 13:11:17 +01:00
|
|
|
done
|
dockerTools.buildImage: support using a layered image in fromImage
Docker images used to be, essentially, a linked list of layers. Each
layer would have a tarball and a json document pointing to its parent,
and the image pointed to the top layer:
imageA ----> layerA
|
v
layerB
|
v
layerC
The current image spec changed this format to where the Image defined
the order and set of layers:
imageA ---> layerA
|--> layerB
`--> layerC
For backwards compatibility, docker produces images which follow both
specs: layers point to parents, and images also point to the entire
list:
imageA ---> layerA
| |
| v
|--> layerB
| |
| v
`--> layerC
This is nice for tooling which supported the older version and never
updated to support the newer format.
Our `buildImage` code only supported the old version, so in order for
`buildImage` to properly generate an image based on another image
with `fromImage`, the parent image's layers must fully support the old
mechanism.
This is not a problem in general, but is a problem with
`buildLayeredImage`.
`buildLayeredImage` creates images with newer image spec, because
individual store paths don't have a guaranteed parent layer. Including
a specific parent ID in the layer's json makes the output less likely
to cache hit when published or pulled.
This means until now, `buildLayeredImage` could not be the input to
`buildImage`.
The changes in this PR change `buildImage` to only use the layer's
manifest when locating parent IDs. This does break buildImage on
extremely old Docker images, though I do wonder how many of these
exist.
This work has been sponsored by Target.
2018-12-04 18:18:06 +01:00
|
|
|
else
|
|
|
|
touch layer-list
|
2015-11-19 13:11:17 +01:00
|
|
|
fi
|
|
|
|
|
|
|
|
chmod -R ug+rw image
|
2016-09-28 01:42:05 +02:00
|
|
|
|
2015-11-19 13:11:17 +01:00
|
|
|
mkdir temp
|
|
|
|
cp ${layer}/* temp/
|
|
|
|
chmod ug+w temp/*
|
2016-03-10 08:29:28 +01:00
|
|
|
|
|
|
|
for dep in $(cat $layerClosure); do
|
2016-09-28 01:42:05 +02:00
|
|
|
find $dep >> layerFiles
|
2016-03-10 08:29:28 +01:00
|
|
|
done
|
|
|
|
|
2016-09-28 01:42:05 +02:00
|
|
|
echo "Adding layer..."
|
|
|
|
# Record the contents of the tarball with ls_tar.
|
2016-09-23 23:10:47 +02:00
|
|
|
ls_tar temp/layer.tar >> baseFiles
|
2016-03-10 08:29:28 +01:00
|
|
|
|
2018-04-12 13:03:56 +02:00
|
|
|
# Append nix/store directory to the layer so that when the layer is loaded in the
|
|
|
|
# image /nix/store has read permissions for non-root users.
|
|
|
|
# nix/store is added only if the layer has /nix/store paths in it.
|
|
|
|
if [ $(wc -l < $layerClosure) -gt 1 ] && [ $(grep -c -e "^/nix/store$" baseFiles) -eq 0 ]; then
|
|
|
|
mkdir -p nix/store
|
|
|
|
chmod -R 555 nix
|
|
|
|
echo "./nix" >> layerFiles
|
|
|
|
echo "./nix/store" >> layerFiles
|
|
|
|
fi
|
|
|
|
|
2016-09-28 01:42:05 +02:00
|
|
|
# Get the files in the new layer which were *not* present in
|
|
|
|
# the old layer, and record them as newFiles.
|
|
|
|
comm <(sort -n baseFiles|uniq) \
|
|
|
|
<(sort -n layerFiles|uniq|grep -v ${layer}) -1 -3 > newFiles
|
|
|
|
# Append the new files to the layer.
|
2018-03-12 18:26:15 +01:00
|
|
|
tar -rpf temp/layer.tar --hard-dereference --sort=name --mtime="@$SOURCE_DATE_EPOCH" \
|
2017-04-16 08:39:02 +02:00
|
|
|
--owner=0 --group=0 --no-recursion --files-from newFiles
|
2016-09-28 01:42:05 +02:00
|
|
|
|
2017-09-28 12:56:23 +02:00
|
|
|
echo "Adding meta..."
|
|
|
|
|
|
|
|
# If we have a parentID, add it to the json metadata.
|
|
|
|
if [[ -n "$parentID" ]]; then
|
|
|
|
cat temp/json | jshon -s "$parentID" -i parent > tmpjson
|
|
|
|
mv tmpjson temp/json
|
|
|
|
fi
|
|
|
|
|
|
|
|
# Take the sha256 sum of the generated json and use it as the layer ID.
|
|
|
|
# Compute the size and add it to the json under the 'Size' field.
|
|
|
|
layerID=$(sha256sum temp/json|cut -d ' ' -f 1)
|
|
|
|
size=$(stat --printf="%s" temp/layer.tar)
|
|
|
|
cat temp/json | jshon -s "$layerID" -i id -n $size -i Size > tmpjson
|
|
|
|
mv tmpjson temp/json
|
|
|
|
|
|
|
|
# Use the temp folder we've been working on to create a new image.
|
|
|
|
mv temp image/$layerID
|
2016-09-28 01:42:05 +02:00
|
|
|
|
2019-04-30 08:42:24 +02:00
|
|
|
# Add the new layer ID to the end of the layer list
|
dockerTools.buildImage: support using a layered image in fromImage
Docker images used to be, essentially, a linked list of layers. Each
layer would have a tarball and a json document pointing to its parent,
and the image pointed to the top layer:
imageA ----> layerA
|
v
layerB
|
v
layerC
The current image spec changed this format to where the Image defined
the order and set of layers:
imageA ---> layerA
|--> layerB
`--> layerC
For backwards compatibility, docker produces images which follow both
specs: layers point to parents, and images also point to the entire
list:
imageA ---> layerA
| |
| v
|--> layerB
| |
| v
`--> layerC
This is nice for tooling which supported the older version and never
updated to support the newer format.
Our `buildImage` code only supported the old version, so in order for
`buildImage` to properly generate an image based on another image
with `fromImage`, the parent image's layers must fully support the old
mechanism.
This is not a problem in general, but is a problem with
`buildLayeredImage`.
`buildLayeredImage` creates images with newer image spec, because
individual store paths don't have a guaranteed parent layer. Including
a specific parent ID in the layer's json makes the output less likely
to cache hit when published or pulled.
This means until now, `buildLayeredImage` could not be the input to
`buildImage`.
The changes in this PR change `buildImage` to only use the layer's
manifest when locating parent IDs. This does break buildImage on
extremely old Docker images, though I do wonder how many of these
exist.
This work has been sponsored by Target.
2018-12-04 18:18:06 +01:00
|
|
|
(
|
2019-04-30 08:42:24 +02:00
|
|
|
cat layer-list
|
dockerTools.buildImage: support using a layered image in fromImage
Docker images used to be, essentially, a linked list of layers. Each
layer would have a tarball and a json document pointing to its parent,
and the image pointed to the top layer:
imageA ----> layerA
|
v
layerB
|
v
layerC
The current image spec changed this format to where the Image defined
the order and set of layers:
imageA ---> layerA
|--> layerB
`--> layerC
For backwards compatibility, docker produces images which follow both
specs: layers point to parents, and images also point to the entire
list:
imageA ---> layerA
| |
| v
|--> layerB
| |
| v
`--> layerC
This is nice for tooling which supported the older version and never
updated to support the newer format.
Our `buildImage` code only supported the old version, so in order for
`buildImage` to properly generate an image based on another image
with `fromImage`, the parent image's layers must fully support the old
mechanism.
This is not a problem in general, but is a problem with
`buildLayeredImage`.
`buildLayeredImage` creates images with newer image spec, because
individual store paths don't have a guaranteed parent layer. Including
a specific parent ID in the layer's json makes the output less likely
to cache hit when published or pulled.
This means until now, `buildLayeredImage` could not be the input to
`buildImage`.
The changes in this PR change `buildImage` to only use the layer's
manifest when locating parent IDs. This does break buildImage on
extremely old Docker images, though I do wonder how many of these
exist.
This work has been sponsored by Target.
2018-12-04 18:18:06 +01:00
|
|
|
# originally this used `sed -i "1i$layerID" layer-list`, but
|
|
|
|
# would fail if layer-list was completely empty.
|
|
|
|
echo "$layerID/layer.tar"
|
2019-06-27 20:15:42 +02:00
|
|
|
) | sponge layer-list
|
dockerTools.buildImage: support using a layered image in fromImage
Docker images used to be, essentially, a linked list of layers. Each
layer would have a tarball and a json document pointing to its parent,
and the image pointed to the top layer:
imageA ----> layerA
|
v
layerB
|
v
layerC
The current image spec changed this format to where the Image defined
the order and set of layers:
imageA ---> layerA
|--> layerB
`--> layerC
For backwards compatibility, docker produces images which follow both
specs: layers point to parents, and images also point to the entire
list:
imageA ---> layerA
| |
| v
|--> layerB
| |
| v
`--> layerC
This is nice for tooling which supported the older version and never
updated to support the newer format.
Our `buildImage` code only supported the old version, so in order for
`buildImage` to properly generate an image based on another image
with `fromImage`, the parent image's layers must fully support the old
mechanism.
This is not a problem in general, but is a problem with
`buildLayeredImage`.
`buildLayeredImage` creates images with newer image spec, because
individual store paths don't have a guaranteed parent layer. Including
a specific parent ID in the layer's json makes the output less likely
to cache hit when published or pulled.
This means until now, `buildLayeredImage` could not be the input to
`buildImage`.
The changes in this PR change `buildImage` to only use the layer's
manifest when locating parent IDs. This does break buildImage on
extremely old Docker images, though I do wonder how many of these
exist.
This work has been sponsored by Target.
2018-12-04 18:18:06 +01:00
|
|
|
|
2017-09-28 12:56:23 +02:00
|
|
|
# Create image json and image manifest
|
2017-08-02 19:27:19 +02:00
|
|
|
imageJson=$(cat ${baseJson} | jq ". + {\"rootfs\": {\"diff_ids\": [], \"type\": \"layers\"}}")
|
|
|
|
manifestJson=$(jq -n "[{\"RepoTags\":[\"$imageName:$imageTag\"]}]")
|
dockerTools.buildImage: support using a layered image in fromImage
Docker images used to be, essentially, a linked list of layers. Each
layer would have a tarball and a json document pointing to its parent,
and the image pointed to the top layer:
imageA ----> layerA
|
v
layerB
|
v
layerC
The current image spec changed this format to where the Image defined
the order and set of layers:
imageA ---> layerA
|--> layerB
`--> layerC
For backwards compatibility, docker produces images which follow both
specs: layers point to parents, and images also point to the entire
list:
imageA ---> layerA
| |
| v
|--> layerB
| |
| v
`--> layerC
This is nice for tooling which supported the older version and never
updated to support the newer format.
Our `buildImage` code only supported the old version, so in order for
`buildImage` to properly generate an image based on another image
with `fromImage`, the parent image's layers must fully support the old
mechanism.
This is not a problem in general, but is a problem with
`buildLayeredImage`.
`buildLayeredImage` creates images with newer image spec, because
individual store paths don't have a guaranteed parent layer. Including
a specific parent ID in the layer's json makes the output less likely
to cache hit when published or pulled.
This means until now, `buildLayeredImage` could not be the input to
`buildImage`.
The changes in this PR change `buildImage` to only use the layer's
manifest when locating parent IDs. This does break buildImage on
extremely old Docker images, though I do wonder how many of these
exist.
This work has been sponsored by Target.
2018-12-04 18:18:06 +01:00
|
|
|
|
2019-04-30 08:42:24 +02:00
|
|
|
for layerTar in $(cat ./layer-list); do
|
dockerTools.buildImage: support using a layered image in fromImage
Docker images used to be, essentially, a linked list of layers. Each
layer would have a tarball and a json document pointing to its parent,
and the image pointed to the top layer:
imageA ----> layerA
|
v
layerB
|
v
layerC
The current image spec changed this format to where the Image defined
the order and set of layers:
imageA ---> layerA
|--> layerB
`--> layerC
For backwards compatibility, docker produces images which follow both
specs: layers point to parents, and images also point to the entire
list:
imageA ---> layerA
| |
| v
|--> layerB
| |
| v
`--> layerC
This is nice for tooling which supported the older version and never
updated to support the newer format.
Our `buildImage` code only supported the old version, so in order for
`buildImage` to properly generate an image based on another image
with `fromImage`, the parent image's layers must fully support the old
mechanism.
This is not a problem in general, but is a problem with
`buildLayeredImage`.
`buildLayeredImage` creates images with newer image spec, because
individual store paths don't have a guaranteed parent layer. Including
a specific parent ID in the layer's json makes the output less likely
to cache hit when published or pulled.
This means until now, `buildLayeredImage` could not be the input to
`buildImage`.
The changes in this PR change `buildImage` to only use the layer's
manifest when locating parent IDs. This does break buildImage on
extremely old Docker images, though I do wonder how many of these
exist.
This work has been sponsored by Target.
2018-12-04 18:18:06 +01:00
|
|
|
layerChecksum=$(sha256sum image/$layerTar | cut -d ' ' -f1)
|
2019-04-30 08:42:24 +02:00
|
|
|
imageJson=$(echo "$imageJson" | jq ".history |= . + [{\"created\": \"$(jq -r .created ${baseJson})\"}]")
|
|
|
|
# diff_ids order is from the bottom-most to top-most layer
|
|
|
|
imageJson=$(echo "$imageJson" | jq ".rootfs.diff_ids |= . + [\"sha256:$layerChecksum\"]")
|
|
|
|
manifestJson=$(echo "$manifestJson" | jq ".[0].Layers |= . + [\"$layerTar\"]")
|
2017-08-02 19:27:19 +02:00
|
|
|
done
|
|
|
|
|
|
|
|
imageJsonChecksum=$(echo "$imageJson" | sha256sum | cut -d ' ' -f1)
|
2017-09-28 12:56:23 +02:00
|
|
|
echo "$imageJson" > "image/$imageJsonChecksum.json"
|
|
|
|
manifestJson=$(echo "$manifestJson" | jq ".[0].Config = \"$imageJsonChecksum.json\"")
|
2017-08-02 19:27:19 +02:00
|
|
|
echo "$manifestJson" > image/manifest.json
|
2017-07-26 21:53:35 +02:00
|
|
|
|
2017-09-28 12:56:23 +02:00
|
|
|
# Store the json under the name image/repositories.
|
|
|
|
jshon -n object \
|
|
|
|
-n object -s "$layerID" -i "$imageTag" \
|
|
|
|
-i "$imageName" > image/repositories
|
|
|
|
|
2016-09-28 01:42:05 +02:00
|
|
|
# Make the image read-only.
|
2015-11-19 13:11:17 +01:00
|
|
|
chmod -R a-w image
|
|
|
|
|
2016-09-28 01:42:05 +02:00
|
|
|
echo "Cooking the image..."
|
2018-04-03 10:26:03 +02:00
|
|
|
tar -C image --hard-dereference --sort=name --mtime="@$SOURCE_DATE_EPOCH" --owner=0 --group=0 --xform s:'^./':: -c . | pigz -nT > $out
|
2016-09-28 01:42:05 +02:00
|
|
|
|
|
|
|
echo "Finished."
|
2015-11-19 13:11:17 +01:00
|
|
|
'';
|
|
|
|
|
|
|
|
in
|
2016-09-28 01:42:05 +02:00
|
|
|
result;
|
2017-08-25 11:47:28 +02:00
|
|
|
|
|
|
|
# Build an image and populate its nix database with the provided
|
|
|
|
# contents. The main purpose is to be able to use nix commands in
|
|
|
|
# the container.
|
|
|
|
# Be careful since this doesn't work well with multilayer.
|
|
|
|
buildImageWithNixDb = args@{ contents ? null, extraCommands ? "", ... }:
|
2018-04-30 15:01:30 +02:00
|
|
|
let contentsList = if builtins.isList contents then contents else [ contents ];
|
|
|
|
in buildImage (args // {
|
2017-08-25 11:47:28 +02:00
|
|
|
extraCommands = ''
|
|
|
|
echo "Generating the nix database..."
|
|
|
|
echo "Warning: only the database of the deepest Nix layer is loaded."
|
|
|
|
echo " If you want to use nix commands in the container, it would"
|
|
|
|
echo " be better to only have one layer that contains a nix store."
|
2018-04-30 15:01:30 +02:00
|
|
|
|
2017-08-25 11:47:28 +02:00
|
|
|
export NIX_REMOTE=local?root=$PWD
|
2018-04-30 15:01:30 +02:00
|
|
|
${nix}/bin/nix-store --load-db < ${closureInfo {rootPaths = contentsList;}}/registration
|
2017-09-13 11:40:26 +02:00
|
|
|
|
|
|
|
mkdir -p nix/var/nix/gcroots/docker/
|
2018-04-30 15:01:30 +02:00
|
|
|
for i in ${lib.concatStringsSep " " contentsList}; do
|
2017-09-13 11:40:26 +02:00
|
|
|
ln -s $i nix/var/nix/gcroots/docker/$(basename $i)
|
|
|
|
done;
|
2017-08-25 11:47:28 +02:00
|
|
|
'' + extraCommands;
|
|
|
|
});
|
2015-11-19 13:11:17 +01:00
|
|
|
}
|