I've got two virtual machines (VMs) set up, one for Sonarr and another for Radarr, running through Docker Compose. Everything was running smoothly until I ran into some memory issues and decided to restart the VMs. After the reboot, both services showed up fine, but trouble hit when I tried to update the Sonarr compose file and reboot it. I got an error message saying the mount source path was on a read-only file system. Upon further investigation, I realized Sonarr was still running, despite the fact that when I tried `docker-compose down`, it seemed to remove the container. The weird part is that when I check with `sudo docker ps`, it shows no running containers, but after stopping and starting the Docker service, Sonarr comes back up. It's confusing because my Docker info says I have zero containers running. How could a container be alive when Docker says there's nothing running? Any insight would be appreciated!
2 Answers
Are you using the Docker snap that comes with Ubuntu? If so, that could be causing issues since it's sandboxed and may mess with your volume mounts. Check your installed snaps using `snap list`. I suggest uninstalling the Docker snap and installing Docker properly using the official documentation.
Absolutely *do not* use the Docker snap install on Ubuntu. Uninstall that version right away and follow the proper installation steps from the documentation to avoid these kinds of problems. It sounds like your version might also be out of date, which can lead to confusion.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures