README
¶
This is a tool to get a list of image sources out of a Dockerfile.
It can also optionally run another program to add a "replace" directive to test out a feature I'm working on to replace images with a different source reference.
This tool only generates metadata that can be fed into other tools. It is based on a lot of in progress work and is only here as a placeholder. Some things are being linked to as a library instead of used as intended (buildkit API calls) because the functionaility is not available in any released buildkit/dockerfile parser yet.
There are absolutely no stability guarentees between releases at this time. A command that worked one way before may behave differently or even not even exist in the next release.
Example Usage
This tool can output data in two formats:
--format=build-flags
- Used to output flags directly todocker buildx build
--format=modfile
- Experimental file which requires a custom syntax parser (--build-arg BUILDKIT_SYNTAX="mcr.microsoft.com/oss/moby/dockerfile:modfile1"
). The file is passed along with the build context and repalcements are by the parser during build.
The default format is build-flags
.
$ ./gnarly --mod-prog=contrib/mod.sh --mod-config=contrib/lookup.json
--build-context docker.io/library/golang:1.18=docker-image://mcr.microsoft.com/oss/go/microsoft/golang:1.18 $
Only sources that have a replacement will be output.
Notice it does not print a newline character so it can be passed directly to docker buildx build
.
When using this format, whatever --build-args
you pass to this tool will also be part of the output so you don't have to specify build-args to both this tool and to `docker buildx build.
With docker buildx build
:
$ docker buildx build $(./gnarly --mod-prog=contrib/mod.sh --mod-config=contrib/lookup.json) .
[+] Building 32.0s (12/12) FINISHED
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 496B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [context golang:1.18] load metadata for mcr.microsoft.com/oss/go/microsoft/golang:1.18 0.0s
=> [context golang:1.18] mcr.microsoft.com/oss/go/microsoft/golang:1.18 0.0s
=> => resolve mcr.microsoft.com/oss/go/microsoft/golang:1.18 0.0s
=> [internal] load build context 0.0s
=> => transferring context: 7.03kB 0.0s
=> CACHED [build 1/7] WORKDIR /go/src/github.com/deislabs/gnarly 0.0s
=> CACHED [build 2/7] COPY go.mod . 0.0s
=> CACHED [build 3/7] COPY go.sum . 0.0s
=> CACHED [build 4/7] RUN --mount=type=cache,target=/go/pkg/mod --mount=type=cache,target=/root/.cache/go-build go mod download 0.0s
=> [build 5/7] COPY . . 0.2s
=> [build 6/7] RUN --mount=type=cache,target=/go/pkg/mod --mount=type=cache,target=/root/.cache/go-build CGO_ENABLED=0 go build . 31.5s
=> [stage-1 1/1] COPY --from=build /go/src/github.com/deislabs/gnarly/gnarly /
For --format=modfile
:
$ ./gnarly --format=modfile --mod-prog=contrib/mod.sh --mod-config=contrib/lookup.json | tee Dockerfile.mod
{
"sources": [
{
"type": "docker-image",
"ref": "docker.io/library/golang:1.18",
"replace": "mcr.microsoft.com/oss/go/microsoft/golang:1.18"
}
]
}
$ docker buildx build --build-arg BUILDKIT_SYNTAX=mcr.microsoft.com/oss/moby/dockerfile:modfile1 .
Here we've told gnarly
to use contrib/mod.sh
as a tool to handle replacements.
The contrib/mod.sh
script uses contrib/lookup.json
as a lookup table for replacements.
For each ref that is found in the Dockerfile by gnarly
, the contrib/mod.sh
is called with the found ref as the first argument. The contrib/mod.sh
script can return an empty string or a replacement ref.
You can specify a path to a config file to use, which will be passed along to the mod-prog as an environment variable MOD_CONFIG
.
The output of this is saved to Dockerfile.mod
which is a special file that the syntax parser shown above will parse to handle replacements.
This also supports a built-in replacement generator.
This takes a config file (passed via --mod-config
) with a list of match/replace rules.
The first match is used for each ref.
[
{"match": "<some matcher>", "replace": "<some value>"}
]
The match
field can be a regex, and the replace
value can make use of capture groups from the regex.
See regexp.ReplaceAllString for more details.
As an example, see contrib/mod-builtin.json
.
In some cases you may not want to modify the main build context with a Dockerfile.mod, which could dirty the git tree or potentially interfere with the actual build. For this case you can use a special "named" context with the mod file in it.
$ dir="$(mktemp -d)" # Make a temp dir where we'll store the Dockerfile.mod
$ ./gnarly --format=modfile --mod-prog=contrib/mod.sh --mod-config=contrib/lookup.json | tee "${dir}/Dockerfile.mod" # Generate the Dockerfile.mod and store it in the temp dir created above.
{
"sources": [
{
"type": "docker-image",
"ref": "docker.io/library/golang:1.18",
"replace": "mcr.microsoft.com/oss/go/microsoft/golang:1.18"
}
]
}
$ docker buildx build --build-arg BUILDKIT_SYNTAX=mcr.microsoft.com/oss/moby/dockerfile:modfile1 --build-context "dockerfile-mod=${dir}" .
[+] Building 2.2s (17/17) FINISHED
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 496B 0.0s
=> resolve image config for mcr.microsoft.com/oss/moby/dockerfile:modfile1 0.3s
=> CACHED docker-image://mcr.microsoft.com/oss/moby/dockerfile:modfile1@sha256:ddccaae065a61196876e89b99eb88ac66cfbc4e21daea9e90f0588dab02420ae 0.0s
=> => resolve mcr.microsoft.com/oss/moby/dockerfile:modfile1@sha256:ddccaae065a61196876e89b99eb88ac66cfbc4e21daea9e90f0588dab02420ae 0.0s
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 496B 0.0s
=> [context dockerfile-mod] load .dockerignore 0.0s
=> => transferring dockerfile-mod: 2B 0.0s
=> [context dockerfile-mod] load from client 0.0s
=> => transferring dockerfile-mod: 36B 0.0s
=> [internal] load metadata for mcr.microsoft.com/oss/go/microsoft/golang:1.18 0.1s
=> [build 1/7] FROM mcr.microsoft.com/oss/go/microsoft/golang:1.18@sha256:fba12e22cb828665f844f123c5bfd5143f8e9c00c960d6abd4653b1b0e35df6c 0.0s
=> => resolve mcr.microsoft.com/oss/go/microsoft/golang:1.18@sha256:fba12e22cb828665f844f123c5bfd5143f8e9c00c960d6abd4653b1b0e35df6c 0.0s
=> [internal] load build context 0.0s
=> => transferring context: 19.10kB 0.0s
=> CACHED [build 2/7] WORKDIR /go/src/github.com/deislabs/gnarly 0.0s
=> CACHED [build 3/7] COPY go.mod . 0.0s
=> CACHED [build 4/7] COPY go.sum . 0.0s
=> CACHED [build 5/7] RUN --mount=type=cache,target=/go/pkg/mod --mount=type=cache,target=/root/.cache/go-build go mod download 0.0s
=> [build 6/7] COPY . . 0.2s
=> [build 7/7] RUN --mount=type=cache,target=/go/pkg/mod --mount=type=cache,target=/root/.cache/go-build CGO_ENABLED=0 go build . 1.2s
=> [stage-1 1/1] COPY --from=build /go/src/github.com/deislabs/gnarly/gnarly /
$ rm -rf "${dir}"
Here we have passed a --build-context
with a value of "dockerfile-mod=${dir}"
.
This is an extra context that buildx will send called dockerfile-mod
.
In the specified BUILDKIT_SYNTAX
, the dockerfile-mod
named context is a special context it will use to look for a Dockerfile.mod
.
This can be a directory, an image, or even a URL. See https://www.docker.com/blog/dockerfiles-now-support-multiple-build-contexts/ for more details on named contexts.
You can also specify a custom name for the named context, but you'll need to set a --build-arg
to tell the builder about that name.
$ docker buildx build --build-arg BUILDKIT_SYNTAX=mcr.microsoft.com/oss/moby/dockerfile:modfile1 --build-context "my-custom-name=${dir}" --build-arg BUILDKIT_MOD_CONTEXT=my-custom-name .
One more thing
This tool can also be used to wrap the docker
cli.
When in this mode the tool looks at the passed in arguments to see if it is an invocation of docker build
or docker buildx build
.
If so it will auto-generate the replacements and inject the neccessary arguments and execute the real docker.
This can be done in one of two ways:
- You can create a symlink (or just call the binary
docker
...) to thegnarly
binary calleddocker
. Any invocation where against this symlink will make it act as a docker wrapper., e.g.ln -s ln -s ./gnarly docker
- In lieu of symlinking or other such methods, you can set the environment variable
DOCKERFILE_MOD_INVOKE_DOCKER=1
, this has the same affect as 1.
This can completely wrap docker (even docker run
, docker exec
, etc).
This should work with 100% of use cases except since it is are trying to generate mod data for builds, remote build contexts (e.g. docker buildx build <URL>
) are not currently supported.
The workaround for this is to pre-generate your mod files and pass the path as an environment variable DOCKERFILE_MOD_PATH=<path to Dockerfile.mod>
.
This workaround is going to be the best way to make sure no builds fail because of some missing functionality in gnarly
.
This will also inject buildx
into a build invocation if docker build
does not support the --build-context
flag.
Example: docker build .
will be changed to docker buildx build .
.
The buildx
subcommand is injected immediately before the build
argument, so it should account for any flags before it.
This also supports passing through some environment variables that will be converted to flags passed to docker buildx build
.
Supported env vars
var name | description | flag output |
---|---|---|
BUILDKIT_METADATA_FILE | Path to output build metadata to | --metadata-file=<path> |
BUILDKIT_SYNTAX | Dockerfile parser image | --build-arg BUILDKIT_SYNTAX |
BUILDKIT_OUTPUT | Spec for outputing build results | --output=<spec> |
BUILDKIT_CACHE_TO | Remote cache spec to forward the build cache to | --cache-to=<spec> |
BUILDKIT_CACHE_FROM | Remote cache spec to populate the build cache with | --cache-from=<spec> |
BUILDKIT_PLATFORM | Platform spec to build, e.g. linux/amd64 |
--platform=<spec> |
BUILDX_LOAD | Bool-like value to tell buildx to load the image into Docker | --load |
BUILDKIT_TAG | CSV list of image tags to override values passed to the docker CLI | -t=<tag> |
BUILDKIT_METADATA_DIR | Directory to store buildkit metadata file with randomly generated name | --metadata-file=<dir>/metadata-<random>.json |
In general this mode is only recommended when you do not have control over the build invocation and as such cannot inject your own build arguments.
There may be some failures with the command line parsing, particularly around how boolean flags are handled. There are some special case handlers for these, but there may be more.
Documentation
¶
There is no documentation for this package.