Every deploy prints removed container netork-registry-1, even on a host where that container has long been gone. The step "Removing retired services" (deploy.sh, RETIRED_CONTAINERS, NetOrk/netork#763) echoes the line whenever docker rm -f succeeds, and docker rm -f exits 0 for a container that does not exist.
docker events shows no create or remove for netork-registry-1 in the hours between two deploys that both reported removing it, and no compose file on the host defines a registry service. The line is false; nothing comes back.
Why it matters
The deploy log is what we read to see what a deploy changed. A line that claims a removal on every run looks like a recurring problem (something recreating the registry), and it hides the run where a removal really happened. The volume branch is fine: docker volume rm fails for a missing volume.
Fix
Only remove, and only report, what exists:
for c in ${RETIRED_CONTAINERS};do
docker inspect "$c" >/dev/null 2>&1&& docker rm -f "$c" >/dev/null &&echo"removed container $c"done
## What happens
Every deploy prints `removed container netork-registry-1`, even on a host where that container has long been gone. The step "Removing retired services" (deploy.sh, `RETIRED_CONTAINERS`, NetOrk/netork#763) echoes the line whenever `docker rm -f` succeeds, and `docker rm -f` exits 0 for a container that does not exist.
Checked on 172.22.8.50 (2026-10-08):
```
$ docker rm -f netork-does-not-exist-xyz >/dev/null 2>&1; echo $?
0
$ docker volume rm netork_does_not_exist_xyz >/dev/null 2>&1; echo $?
1
```
`docker events` shows no create or remove for `netork-registry-1` in the hours between two deploys that both reported removing it, and no compose file on the host defines a registry service. The line is false; nothing comes back.
## Why it matters
The deploy log is what we read to see what a deploy changed. A line that claims a removal on every run looks like a recurring problem (something recreating the registry), and it hides the run where a removal really happened. The volume branch is fine: `docker volume rm` fails for a missing volume.
## Fix
Only remove, and only report, what exists:
```sh
for c in ${RETIRED_CONTAINERS}; do
docker inspect "$c" >/dev/null 2>&1 && docker rm -f "$c" >/dev/null && echo "removed container $c"
done
```
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.
What happens
Every deploy prints
removed container netork-registry-1, even on a host where that container has long been gone. The step "Removing retired services" (deploy.sh,RETIRED_CONTAINERS, NetOrk/netork#763) echoes the line wheneverdocker rm -fsucceeds, anddocker rm -fexits 0 for a container that does not exist.Checked on 172.22.8.50 (2026-10-08):
docker eventsshows no create or remove fornetork-registry-1in the hours between two deploys that both reported removing it, and no compose file on the host defines a registry service. The line is false; nothing comes back.Why it matters
The deploy log is what we read to see what a deploy changed. A line that claims a removal on every run looks like a recurring problem (something recreating the registry), and it hides the run where a removal really happened. The volume branch is fine:
docker volume rmfails for a missing volume.Fix
Only remove, and only report, what exists: