Control: severity -1 wishlist Control: tag -1 help Hadmut Danisch <had...@danisch.de> writes:
> the debian package for the docker-registry is built to run exactly one > instance with exactly one config file. This is correct, and keeps the package easy and simple to use for the intended use-case. > However, the docker-registry is limited in its capabilities, it can > either run as a local private registry for your own images, or it can > act as a proxy/cache for exactly one upstream server. > > In Reality, one would need more than one instance to run, e.g. one as a > store for local images, one as a proxy/cache for docker.io, and so on. In those cases, I would probably want to run the docker-registry inside a (podman) container anyways, where the "single-instance" assumption still holds. > > > I'd therefore propose: > > > - turn the systemd unit into a template (basically put a @ in the > filename and replace some data with %i , and run the registry with > > /etc/docker/registry/%i.yml > > i.e. allow to run an arbitrary number of instances for different > purposes. > > > - maybe give two example config files, i.e. one for the store of local > home made images at Port 5000, and a second as a cache/proxy for > docker.io at Port 5001. That sounds reasonable to me. I'm not that familiar with writing systemd unit files myself, but I'd be happy to review a patch for the described functionality and an upgrade path for existing systems. Thanks! -rt
