github/dokku
0
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Merge pull request #8669 from dokku/8630-ps-restart-and-other-commands-fail-after-local-image-gc-when-registry-push-on-release-is-enabled

Browse Source 
Recover deployed image from registry on local miss
This commit is contained in:
Jose Diaz-Gonzalez
2026-05-26 21:09:15 -04:00
committed by GitHub
parent e30b6d2ac4 b45c86dcc9
commit f9186ca1fd
9 changed files with 155 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/advanced-usage/registry-management.md
View File

@@ -178,6 +178,10 @@ dokku registry:set node-js-app push-on-release
dokku registry:set --global push-on-release
```
#### Recovering from local image GC
When `push-on-release` is enabled, Dokku treats the remote registry as the canonical store for app images. If a local image disappears - for example because a `docker image prune` cron ran, the host rebooted, or an operator removed it manually - subsequent commands that need the image (`ps:restart`, `ps:scale`, `dokku run`, `domains:add`, `certs:add`, etc.) will pull the missing tag back from the registry automatically. Per-app registry credentials configured via `registry:login` are honored during the pull. This recovery covers the deployed numeric tag pushed by the registry plugin - a missing `latest` tag will be ignored.
### Push extra tags
To push the image on release with extra tags, set the `push-extra-tags` to a comma-separated list of tags via the `registry:set` command. The default value for this property is empty. Setting the property will result in the image being tagged with extra tags every release.