-
-
Notifications
You must be signed in to change notification settings - Fork 51
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] container starting issues on QNAP systems #158
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Hello @j0nnymoe |
The short answer is no, we really don't want to because it will mask actual issues that non-QNAP users experience and lead to broken containers that are hard to troubleshoot. We only added the workaround for Swag because a change we made to the init process unintentionally caused previously working containers to break for people experiencing this QNAP bug. QNAP need to fix this upstream. |
Hello, What steps do I need to take to resolve the bad address issue? Is it enough to simply use the image linked here https://github.com/linuxserver/docker-swag/pull/523#issuecomment-2481285195 I’ve already tried using the image, but the issue persists. Thanks `[env-init] CF_TUNNEL_CONFIG set from FILE__CF_TUNNEL_CONFIG
Brought to you by linuxserver.io To support the app dev(s) visit: To support LSIO projects visit: ─────────────────────────────────────── User UID: 1000 using keys found in /config/keys chmod: changing permissions of '/defaults/etc/letsencrypt/renewal-hooks/deploy': Bad address <-------------------------------------------------> |
Why would you use an dev build of swag in place of the mariadb image? |
Apologies for posting in the wrong section; please disregard this. |
Is there an existing issue for this?
Current Behavior
Hello,
the issue is basically the same as linuxserver/docker-swag#514 and probably affects all linuxserver images that are running on QNAP.
Can you apply the workaround from linuxserver/docker-swag#523 to all your images? That would be really nice :)
Hopefully this will be fixed soon by QNAP.
Expected Behavior
No response
Steps To Reproduce
Run the container on a current QNAP Container Station
Environment
CPU architecture
x86-64
Docker creation
default CLI command from README.md
Container logs
The text was updated successfully, but these errors were encountered: