I’m running storagenode, as a Docker on my Synology.
So far, so good.
Apparently, there was a power outage and Synology rebooted (I have UPS, not sure, why it didn’t help).
So, at some point today, I went to check the status and I see, that the storagenode is not running. By the way, the watchtower container was running.
So, I tried to start it and got:
docker: Error response from daemon: Conflict. The container name “/storagenode” is already in use by container "f6d49…
Here is my docker command:
sudo docker run -d \ --restart unless-stopped \ -p ***:***\ -p 14002:14002 \ -e WALLET="0x***" \ -e EMAIL="***" \ -e ADDRESS="***:***" \ -e BANDWIDTH="20TB" \ -e STORAGE="6TB" \ --mount type=bind,source="/volume1/storj/Identity/storagenode",destination=/app/identity \ --mount type=bind,source="/volume1/storj/data/",destination=/app/config \ --name storagenode \ storjlabs/storagenode:beta
I know, how to fix that (
sudo docker rm storagenode fixed the issue).
But I’m wondering, why it did not successfully started by itself? Could
watchtower do anything about it? Perhaps, remove dead container?