Package: docker-registry Version: 2.8.2+ds1-1 Severity: wishlist X-Debbugs-Cc: had...@danisch.de
Dear Maintainer, the debian package for the docker-registry is built to run exactly one instance with exactly one config file. 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. 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. best regards Hadmut -- System Information: Debian Release: 12.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.2.0-35-generic (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages docker-registry depends on: ii adduser 3.134 ii init-system-helpers 1.65.2 ii libc6 2.36-9+deb12u3 ii sysvinit-utils [lsb-base] 3.06-4 docker-registry recommends no packages. docker-registry suggests no packages. -- no debconf information
