-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
[BUG] Trying to upgrade from 4.1.0.6175-ls141 to latest #213
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
What model Synology? |
Docker Info:
Synology HW version: DS1512+ |
any thoughts? |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
its still happening. any ideas are welcome |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Still unresolved |
Your CPU does not support the needed instructions used by alpine 3.15, which manifests in wierd errors like this. |
Is there an existing issue for this?
Current Behavior
When I switch my docker-compose to pull the latest Radarr image, Radarr never actually starts up. The whole log file can be seen below:
No matter what I do it just sits on the custom-init and never gets past it.
Expected Behavior
Fire up and finish starting up
Steps To Reproduce
See that things start up as expected.
Switch to this compose:
Watch it get stuck on the line above and never move past it.
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: