I'm having issues with my Docker containers on Synology. Sometimes, when I modify configurations, I need to stop and restart them, but I run into errors like 'No such container' or 'Container does not exist' even though the container seems to be running fine. For instance, the container names sometimes get prefixed with random strings (like '6218eed231d0_n8n'), and when I try to stop or open these containers, I get errors saying they don't exist. Currently, the only way I can restart them is by stopping the entire Container Manager app through the Synology Package Manager and then starting it back up, which is a hassle since I have over 10 containers. Is there a better way to handle this?
5 Answers
I've encountered similar issues, even with Docker Compose. The quickest fix is often just to restart the NAS. It can be annoying, though!
Do you have a configured compose file for your containers? It can make managing them much easier!
Yes, I’m using a compose file for all my dockers.
Have you thought about managing your containers with Portainer? It has a nice UI and can help with issues like this.
I haven't used Portainer yet. Is it worth switching to?
I used to struggle with this too while using the Synology GUI. It can be really buggy and often gets out of sync with Docker. I switched to using Docker Compose through SSH, which is much more reliable. If something messes up, you can just run `docker compose up -d --force-recreate` to fix it without needing to restart the whole Container Manager! It really saves time.
Thank you! I will give it a try!
Instead of using container names in your Docker commands, try using the container ID. Any luck with that approach?
I typically define the container name in the compose file, but I'll give it a shot removing it. Thanks for the suggestion!
Restarting the Container Manager usually does the trick, but yes, it's time-consuming. I worry that frequently restarting might affect the lifespan of my HDDs.