We've changed the default config path file from
to the one that no longer references docker.
The same goes for the entrypoint shell script.
We've also updated the default config file.
Signed-off-by: Milos Gajdos <milosthegajdos@gmail.com>
official image container.
This conforms to the official image rules to run the container with a shell
without using the --entrypoint flags.
Supports:
[o] docker run registry sh # /bin/sh
[o] docker run -v /a:/b registry /b/config.yml # /bin/registry serve /b/config.yml
[o] docker run registry # /bin/registry serve /etc/docker/config.yml
[o] docker run -ti registry -h # /bin/registry -h
[o] docker run <command> [args] # /bin/registry <command> [args]
Signed-off-by: Richard Scothern <richard.scothern@docker.com>
can be run as so:
docker run --rm --volume /etc/docker-registry.conf:/etc/docker-registry.conf \
registry:2 /etc/docker-registry.conf
See:
https://github.com/docker/distribution/issues/1631
Signed-off-by: Richard Scothern <richard.scothern@gmail.com>
This is based on swarm-library-image.
Unfortunately, the registry binary needs to be checked in - otherwise
"docker build" wouldn't work without preparation, as is required of
official images. The binary checked in here is from distribution's
current master branch (4cc4d440f6afc7b27c2220993d01a4e2889d87c0). It
will need to be updated to the release version after each release.
Rather than creating a container from scratch, this library image is
based on the ubuntu container, because registry is a dynamically linked
binary.
Because we're using the ubuntu container as a base, manual installation
of ca-certificates.crt isn't necessary. If we end up switching to a
scratch container, this will need to be re-added.
Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>
Milos Gajdos