Closed vertIcod3r closed 8 months ago
Hi.
Does reverting to 2.2.8 fix the issue ?
https://info.linuxserver.io/issues/2023-12-30-synology/
Known Issue: curl endless loop with 3.x Kernels
December 30, 2023 at 6:00 PM Known Issues synology alpine
◆ This issue is not resolved yet There is a known issue with the version of curl currently shipped with Alpine 3.19 and 3.x kernels, causing an endless loop to hang containers, usually on startup. The 3.x kernel line has been End of Life since 2017, but some prebuilt systems such as older Synology NAS units are still running it. At time of posting, around 10% of our images have already been rebased to Alpine 3.19 and are therefore affected by this issue, and this number will continue to rise over the next few months.
While a fix has been applied to the affected upstream library we do not have an ETA for if or when it will find its way into the version of curl shipped with Alpine 3.19.
Workaround As a workaround you can revert to an older tag from before the image was rebased to Alpine 3.19, but please be aware that older tags do not receive updates. Refer to the Changelog in the Readme to see when the change was made for a given image. For Unraid users this will require you to edit the container and under the Advanced options change the Repository to append the required tag.
Looks pretty much like the same issue to me 😞
Sure looks like it @buchdag and yes 2.2.8 is working fine. So have to wait for the fix to trickle down. Or see if updating to a newer kernel is possible. Thanks for finding this one.
If your are using the latest image tag and recently updated your image: please make sure you've checked the required read on the project's README.
HTTPS does not work / certificate aren't created : please check in your acme-companion container logs if an authorization or verify error is mentioned, if it is please do the following before opening an issue:
Bug description
After the update to 2.2.9 certificate creation is no longer successful. The command: "curl -s --unix-socket /var/run/docker.sock -X GET http://localhost/containers/json" seems to hang on the container. Utilizing 100% cpu. The only output on the docker logs for the acme container is: "Info: running acme-companion version v2.2.9"
acme-companion image version
Info: running acme-companion version v2.2.9
If this first log line isn't present you are using a v1 image: please provide the tagged version you are using. If you are not using a tagged version latest, please try again with a tagged release before opening an issue (the last v1 tagged release is v1.13.1).
nginx-proxy's Docker configuration
Even with the basic docker compose from the docs:
rendered nginx configuration
Containers logs
nginx-proxy-acme:
nginx-proxy:
Docker host