-
-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sonarr unable to load, seems to be crashing #258
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Does running with seccomp=unconfined as per https://docs.linuxserver.io/faq#jammy allow it to run without crashing? |
yep... missed that part thanks |
Out of interest, could you post the output of While the seccomp fix works for you, it's not a solution per se, it's a workaround, and having the latest docker engine should mean things just work without it, so I'm curious as to why they don't. |
Hi, have the same issue, seccomp=unconfined helped. Here is my output if it helps:
|
Is there an existing issue for this?
Current Behavior
Sonarr is crashing. Shows running, but unable to access the UI.
found the issue #251 and was told to write up a new bug report with my information.
Expected Behavior
should be able to access the UI for Sonarr
Steps To Reproduce
Ubuntu 20.04 with docker 23.0.1 installed via docker compose. Running on Sonarr:latest I am unable to get to the IP:8989 of the container and just shows that the container is down or is not able to connect to it. running 'docker container ls' it would show it running and up, but there was no way to access it.
I ended up rolling back to a previous image I still had to get it back up and running.
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: