The deploy ended with docker image prune -af: every image no container uses at that moment, on a host that may run other things too. The KB's copy of the same line took the license server's rollback images on compute-01 on 2026-10-23 (NetOrk/kb-server#157). The line came from here, written when every target was netOrk's alone. On a customer host that also runs other things, it removes their images too.
Changes
Before the swap, deploy.sh records the image IDs netOrk's own containers use (compose ps -aq … | xargs docker inspect --format '{{.Image}}').
After the verification and the migration it hands those IDs to the new remote/remove_replaced_images.sh. The script removes each image by its tags, or by its ID once a moving tag such as latest-dev left it without one. It keeps any image a container (netOrk's or anyone else's) still uses; a redeploy of the same tag therefore replaces nothing.
README step 12 describes the new behaviour.
Testing
tests/test_remote_replaced_images.py runs the script against a fake docker and covers five cases:
the replaced release goes by every tag;
an image in use stays;
another project's image is never named;
an untagged leftover goes by its ID;
nothing to remove is no failure.
tests/test_deploy_replaced_images.py: no prune -af; the IDs are recorded before the recreate and removed after the migration, through the script.
Full suite: 82 passed. shellcheck is clean.
## Summary
The deploy ended with `docker image prune -af`: every image no container uses at that moment, on a host that may run other things too. The KB's copy of the same line took the license server's rollback images on compute-01 on 2026-10-23 (NetOrk/kb-server#157). The line came from here, written when every target was netOrk's alone. On a customer host that also runs other things, it removes their images too.
## Changes
- Before the swap, `deploy.sh` records the image IDs netOrk's own containers use (`compose ps -aq … | xargs docker inspect --format '{{.Image}}'`).
- After the verification and the migration it hands those IDs to the new `remote/remove_replaced_images.sh`. The script removes each image by its tags, or by its ID once a moving tag such as `latest-dev` left it without one. It keeps any image a container (netOrk's or anyone else's) still uses; a redeploy of the same tag therefore replaces nothing.
- README step 12 describes the new behaviour.
## Testing
- `tests/test_remote_replaced_images.py` runs the script against a fake `docker` and covers five cases:
- the replaced release goes by every tag;
- an image in use stays;
- another project's image is never named;
- an untagged leftover goes by its ID;
- nothing to remove is no failure.
- `tests/test_deploy_replaced_images.py`: no `prune -af`; the IDs are recorded before the recreate and removed after the migration, through the script.
- Full suite: 82 passed. shellcheck is clean.
The deploy ended with docker image prune -af: every image no container
used at that moment. On a host that runs other things too, that takes
their rollback images; the KB's copy of this line did exactly that on
compute-01 (NetOrk/kb-server#157).
deploy.sh now records the image IDs netOrk's own containers use before
the swap and, after the verification and the migration, hands them to
remote/remove_replaced_images.sh. It removes each by its tags, or by its
ID once a moving tag left it without one, and keeps any image a
container still uses: a redeploy of the same tag replaces nothing.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
The deploy ended with
docker image prune -af: every image no container uses at that moment, on a host that may run other things too. The KB's copy of the same line took the license server's rollback images on compute-01 on 2026-10-23 (NetOrk/kb-server#157). The line came from here, written when every target was netOrk's alone. On a customer host that also runs other things, it removes their images too.Changes
deploy.shrecords the image IDs netOrk's own containers use (compose ps -aq … | xargs docker inspect --format '{{.Image}}').remote/remove_replaced_images.sh. The script removes each image by its tags, or by its ID once a moving tag such aslatest-devleft it without one. It keeps any image a container (netOrk's or anyone else's) still uses; a redeploy of the same tag therefore replaces nothing.Testing
tests/test_remote_replaced_images.pyruns the script against a fakedockerand covers five cases:tests/test_deploy_replaced_images.py: noprune -af; the IDs are recorded before the recreate and removed after the migration, through the script.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.