-
-
Notifications
You must be signed in to change notification settings - Fork 247
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] latest release container 3.0.1-ls339 won't start #522
Comments
It it possible to refer to a previous image in compose file? |
It's the same as on the CLI: Just add a colon after the image name:
|
It works perfectly, thank you! |
See https://discord.com/channels/354974912613449730/1307683867553038417 We'll try and get a workaround in place asap but the underlying issue is on QNAP to fix. |
@thespad sorry I don't have a Discord account |
TL;DR we made a change yesterday that inadvertently turned the existing QNAP issue into a breaking one. |
Ok, then I will stay on the latest working version. |
Is there an existing issue for this?
Current Behavior
Hello,
I have the same problem that @alien75 described in #514. The latest SWAG release
3.0.1-ls339
won't start.The s6 service
init-permissions-config
fails with exit code 1.Please ignore the
chmod
Bad address
errors in the log below. They are already handled by issue #514.Expected Behavior
The container starts without issues.
Current workaround: Downgrade the image to version
3.0.1-ls338
Steps To Reproduce
Start version
3.0.1-ls339
with the default environment variables as described in the README.Doing the same with version
3.0.1-ls338
works.Environment
CPU architecture
x86-64
Docker creation
As described in the README. Additionally I used the following env variables: -e PUID=1003 \ -e PGID=100 \ -e VALIDATION=dns \ -e DNSPLUGIN=cloudflare \ -e SUBDOMAINS=wildcard
The text was updated successfully, but these errors were encountered: