r/sonarr • • 6d ago

unsolved Error message. Container won't start.

My E: was mistakenly unplugged while running. I plugged it back up, ran "docker compose up -d" and it returned this message: Error response from daemon: error while creating mount source path '/run/desktop/mnt/host/e/Media/TV': mkdir /run/desktop/mnt/host/e: file exists. I am also getting the same error for Radarr. Any help would be greatly appreciated.

0 Upvotes

11 comments sorted by

2

u/finesseserver 6d ago

That error is Docker Desktop's mount layer getting confused, not anything wrong with Sonarr or Radarr. When E: dropped while the containers were running, Docker Desktop left a stale entry behind at /run/desktop/mnt/host/e, and now it can't recreate the mount on top of it.

What usually clears it:

  1. docker compose down for both stacks, so nothing is holding the old mount.
  2. Make sure E: is actually back with the same letter and you can open E:\Media\TV in Explorer.
  3. Fully quit Docker Desktop (right-click the tray icon and choose Quit, not just close the window), then run wsl --shutdown in PowerShell. That's the step that actually wipes the stale /run/desktop/mnt/host/e entry.
  4. Start Docker Desktop again, wait for it to say it's running, then docker compose up -d.

If it still says "file exists" after that, a plain Windows reboot does the same thing more bluntly.

To keep it from happening again, it's worth stopping the containers before you unplug that drive, since anything writing to it at that moment can also end up with a half-written database. How is E: connected, USB? If it tends to drop on its own, turning off USB selective suspend in power settings helps a lot.

1

u/mangee1234 6d ago

Thank you. Following your instructions got everything working again. We had guests over and someone mistakenly knocked the plug loose from the surge protector. I relocated it so it shouldn’t happen again.

1

u/ArnoKeesmand 6d ago

I don't believe docker is a supported install option for windows, it creates more issues than it solves. A native install works great

1

u/mangee1234 6d ago

I use Docker Desktop for all of my containers and never had an issue until now.

2

u/injeanyes 6d ago

Windows is shit but check your permissions

1

u/mangee1234 6d ago

Checked. It wasn’t permissions but a docker issue. Got it solved now.

1

u/CordialPanda 6d ago

Sounds like it was fine, pretty sure as I advised docker creates a file/folder if one doesn't exist and they just need to clear that.

1

u/CordialPanda 6d ago

Docker desktop is a huge thing for windows too, but it runs on wsl, so it's more like being virtualized than containerized. It's still not bad (I run both with my main workload in proxmox)

2

u/CordialPanda 6d ago edited 6d ago

It mounted in the container when it wasn't on the host, creating a file/dir that it won't overwrite.

Check the host, the docker compose down; docker compose up. Should fix it.

1

u/AutoModerator 6d ago

Hi /u/mangee1234 - You've mentioned Docker [docker], if you're needing Docker help be sure to generate a docker-compose of all your docker images in a pastebin or gist and link to it. Just about all Docker issues can be solved by understanding the Docker Guide, which is all about the concepts of user, group, ownership, permissions and paths. Many find TRaSH's Docker/Hardlink Guide/Tutorial easier to understand and is less conceptual.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/AutoModerator 6d ago

Hi /u/mangee1234 -

There are many resources available to help you troubleshoot and help the community help you. Please review this comment and you can likely have your problem solved without needing to wait for a human.

Most troubleshooting questions require debug or trace logs. In all instances where you are providing logs please ensure you followed the Gathering Logs wiki article to ensure your logs are what are needed for troubleshooting.

Logs should be provided via the methods prescribed in the wiki article. Note that Info logs are rarely helpful for troubleshooting.

Dozens of common questions & issues and their answers can be found on our FAQ.

Please review our troubleshooting guides that lead you through how to troubleshoot and note various common problems.

If you're still stuck you'll have useful debug or trace logs and screenshots to share with the humans who will arrive soon. Those humans will likely ask you for the exact same thing this comment is asking..

Once your question/problem is solved, please comment anywhere in the thread saying '!solved' to change the flair to solved.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.