Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

DOCKER CONTAINER OF SPECIFIC NAME KEEPS STOPPING

Featured Replies

I really hope someone can help me as this is very strange

 

I had a sonarr docker container which was working fine, but then suddenly would only run for 5 minutes without stopping.

I don't think that the issue is actually with sonarr itself though. It seems to be the name of the container causing the issue, not what is in it.

 

My original container was called "sonarr". I recreated an identical copy of the container with a different name - "sonarr2" - and it ran for several hours. I then stopped the container, deleted the old "sonarr" container and renamed the new one to "sonarr". The container stopped after ~5 minutes. I changed it to "sonarr2" again and it ran for several hours again. I repeated this name change several times with the same result - "sonarr" always stops after ~5 minutes, "sonarr2" never stopped. It ran as "sonarr2" for nearly a week (before I stopped it myself). 

 

Also, the "sonarr" container does actually work perfectly for the 5 minutes it actually remains running.

 

What can possibly have happened? Can I somehow "clear" the seemingly wonky "sonarr" name so I can use it again?

 

This is a chunk of server logs from when I was renaming containers
https://pastebin.com/DYajFwp8 

 

This is my Docker run command

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='sonarr2' --net='bridge' -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -p '8989:8989/tcp' -v '/dev/rtc':'/dev/rtc':'ro' -v '/mnt/user/Videos/':'/tv':'rw' -v '/mnt/user/Downloads/':'/downloads':'rw' -v '/mnt/user/mount_rclone/dropbox/To Mum & Dad/':'/export':'rw' -v '/mnt/user/Downloads/Scripts/':'/scripts':'rw' -v '/mnt/user/appdata/sonarr':'/config':'rw' --security-opt seccomp=unconfined 'linuxserver/sonarr'
704bcfa29e947831767a7c3970cd6591abfe529faa326049f7fbd7cf4c176f37

 

I have been told on the sonarr forum that there is nothing amiss in the sonarr logs - they just stop logging when the container stops, but these are some debug logs from a stopping incident
https://pastebin.com/16Xb15FV 

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.