Skip to content
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

Docker container unresponsive after one automatic cron renewal #6189

Closed
dwlfrth opened this issue Jan 6, 2025 · 8 comments
Closed

Docker container unresponsive after one automatic cron renewal #6189

dwlfrth opened this issue Jan 6, 2025 · 8 comments

Comments

@dwlfrth
Copy link

dwlfrth commented Jan 6, 2025

Followed the instructions to run acme.sh in a Docker container: https://github.com/acmesh-official/acme.sh/wiki/Run-acme.sh-in-docker

Everything works perfectly.
The day later, trying to shut down the container, it simply spins without any output.
Actually, any kind of interaction with the container simply "fails" (without any output since it seems to be spinning forever...)

@dwlfrth
Copy link
Author

dwlfrth commented Jan 6, 2025

Already upgraded...
Unfortunately, cannot provide any type of log since the container is simply unresponsive...
BTW, i do know my way around containers. I've been using them, for over 4 years. Maybe I am doing something wrong but nothing "obvious" (i think)

@dwlfrth
Copy link
Author

dwlfrth commented Jan 6, 2025

root@icinq:/docker/_infra# docker-compose down acme.infra
[+] Running 0/1
⠿ Container acme.infra Error while Stopping 2000.3s
canceled

@dwlfrth
Copy link
Author

dwlfrth commented Jan 6, 2025

That is the output of the automatic cron "renewal"

root@icinq:/home/derek# docker logs -f acme.infra
[Mon Jan 6 01:02:01 UTC 2025] ===Starting cron===
[Mon Jan 6 01:02:02 UTC 2025] Already up to date!
[Mon Jan 6 01:02:02 UTC 2025] Upgrade successful!
[Mon Jan 6 01:02:02 UTC 2025] Automatically upgraded to: 3.1.0
[Mon Jan 6 01:02:02 UTC 2025] Renewing: 'DOMAIN'
[Mon Jan 6 01:02:02 UTC 2025] Renewing using Le_API=https://acme.zerossl.com/v2/DV90
[Mon Jan 6 01:02:02 UTC 2025] Skipping. Next renewal time is: 2025-03-06T01:00:01Z
[Mon Jan 6 01:02:02 UTC 2025] Add '--force' to force renewal.
[Mon Jan 6 01:02:02 UTC 2025] Skipped DOMAIN
[Mon Jan 6 01:02:02 UTC 2025] ===End cron===

@CamelT0E
Copy link

CamelT0E commented Jan 6, 2025

[Mon Jan 6 01:02:02 UTC 2025] Skipping. Next renewal time is: 2025-03-06T01:00:01Z

your certificate is within the first 60 days then the update will be skipped. the certificate will only be updated on 06.03.2025 after the first 60 days have elapsed.

It's all right. If you want to update the certificate beforehand, use the --force flag.

[Mon Jan 6 01:02:02 UTC 2025] Add '--force' to force renewal.

@dwlfrth
Copy link
Author

dwlfrth commented Jan 7, 2025

I do understand that.
The issue here is the container being unresponsive...
I posted the logs since the bot asked me to ;)

@acmesh-official acmesh-official deleted a comment from github-actions bot Jan 10, 2025
@Neilpang
Copy link
Member

Neilpang commented Jan 11, 2025

what do you mean by unresponsive ?

I tried to docker stop acme.sh, it just exits immediately.

How can I reproduce the issue ?

@Neilpang
Copy link
Member

BTW, did you use the latest docker image?

docker pull  neilpang/acme.sh

@dwlfrth
Copy link
Author

dwlfrth commented Jan 11, 2025

Closed, no longer needed

@dwlfrth dwlfrth closed this as completed Jan 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants