On 31.08.24 16:12, Reinhard Tartler wrote:
Do you have thoughts on how do we provide an upgrade path from
existing systems to this new file?
Soft way:
Just add this template to the package (it will do no harm unless
actived) and write a README (and a hint into registry.conf) for multi
instance use:
1. explain why
2. tell not to run the single instance version and the multi instance at
the same time, i.e. systemctl disable --now registry
3. foreach conf file run systemctl enable --now registry@name e.g.
registry@registry
Hard way:
remove the single version unit file from the package and put the
template in instead
in the prepare script mv old /var/lib/docker-registry/* files into
/var/lib/docker-registry/registry/* ( or name it "default")
execute systemctl enable --now docker-registry@registry (or
something like docker-registry@default)
So it will (if registry.conf has not been modified) run as before and
most people will not notice that
1. the path has moved from /var/lib/docker-registry to
/var/lib/docker-registry/registry
2. the unit name is change from docker-registry to docker-registry@default
But this leaves the door open to run as many instances as needed.
Explain in README.
regards
