`docker rm -f` exits 0 for a container that does not exist, so the
"Removing retired services" step printed "removed container
netork-registry-1" on every deploy of every host, long after the
container was gone. That read as something recreating the registry
each time, and it would hide the one deploy that really removed it.
Check with `docker inspect` first, so only an existing container is
removed and reported. The volume branch needed nothing: `docker volume
rm` already fails for a missing volume.
Closes#7
netOrk's docker-compose.yml shipped a registry:2 for the satellite image,
and this script started it on every deploy as infrastructure. Satellites
pull from registry.netork.io; on 172.22.8.50 the registry held one old
image, nothing had pulled from it in 30 days, and it accepted anonymous
pushes on port 5000 of every instance (NetOrk/netork#763).
- registry leaves INFRA_SERVICES.
- A new step removes services netOrk no longer ships: the container
netork-registry-1, then the volume netork_registry_data. `docker
compose up` never removes a container whose service left the compose
file, so without this each host would keep it until someone removed it
by hand. The step is idempotent and works with the old compose file as
well as the new one, so it can go out before netOrk drops the service.