Repository navigation
v2.21.0
This release gives the Zot registry longer request time limits and adds pull-only registry accounts. It also stops a verbose run from printing the registry admin password.
Added
- Zot: new variables
zot_http_read_timeoutandzot_http_write_timeout(rolezot, default"30m"). They renderhttp.readTimeoutandhttp.writeTimeoutinconfig.json. Zot's own default is 60s, an absolute limit for the whole request or response body. A layer upload that still streamed at 60s was cut: zot loggedi/o timeoutand the proxy answered 502. A large pull on a slow link was cut the same way.""renders nothing (zot's 60s)."0s"turns a limit off. The deploy refuses a value that is not a Go duration. The keys need zot v2.1.17 or later; the role pins v2.1.22. - Zot: new variable
zot_pull_users(rolezot, default[]), a list ofusernameandpassword. Each entry is an htpasswd account that can only read (pull) every repository. Thedocker_registriesentry forzot_domainstays the only account that can push and delete. With at least one entry,config.jsongetshttp.accessControl:readon**for the pull accounts, and every action for the admin throughadminPolicy. With the list empty the block is absent and zot has one account, as before. The deploy refuses an entry without a username or a password, a username that does not match^[a-z0-9][a-z0-9._-]{0,62}$, a duplicate, and the admin username. A machine logs in withdocker login <zot_domain> -u <username>. A pull account cannot write a buildx registry cache (git_deploy_registry_cache). - Traefik: new variable
traefik_public_read_timeout(roletraefik, default""). It sets the request read limit of the publicwebsecureentrypoint, with and withouttraefik_split_entrypoints. It applies to every router on that host. Set it only on the host that serves the registry, when machines push over the public address. Empty renders nothing, sotraefik.ymlis unchanged and Traefik keeps its 60s default. The deploy refuses a value that is not whole seconds or a Go duration. - Docs:
docs/build-strategies.mdhas a new section "Registry accounts and time limits".docs/build-pipeline.mdhas a troubleshooting entry for a push that fails at exactly 60 seconds.
Changed
- Zot:
htpasswdnow holds the admin line plus one line per pull account. It still changes only when something changed. The role verifies each account withhtpasswd -iv(password on stdin), and a read-only probe compares the user names in the file with the wanted names. When either check fails, the role writes the whole file again and restarts zot. So a removed pull account and an unknown line added by hand also disappear. Both probes run in check mode too.
Fixed
- Zot: the task that reads the admin account from
docker_registrieshad nono_log, so a run with-vprinted the registry admin password. It now hasno_log: true.
Upgrade notes
- Zot restarts once. The first run that applies the
zotrole on the registry host after the upgrade writes the two new time limits intoconfig.jsonand restarts zot. That isbay upon that env, or abay deploythat runs the rig roles. Other regions pull from this registry, so run the registry host's env first, or runbay deploy <env> --tags zotthere before the others. To keep zot's old 60s limits and skip the restart, set bothzot_http_read_timeoutandzot_http_write_timeoutto"". - Pull accounts are opt-in. Put each password in the vault, add
zot_pull_usersto the group_vars of the registry host, and runbay deploy <env> --tags zot. The role rewriteshtpasswdandconfig.jsonand restarts zot once. A deployment host can use a pull account through its owndocker_registriesentry forzot_domain. The registry host and the build server must keep the admin entry. - The public entrypoint limit is opt-in. Nothing changes until you set
traefik_public_read_timeout. When machines push to the registry over its public address, set it (for example"30m") on the registry host and runbay deploy <env> --tags traefik. Traefik restarts once.