Open tpf4oc opened 1 week ago
Please upgrade to the latest code and try again first. Maybe it's already fixed. acme.sh --upgrade
If it's still not working, please provide the log with --debug 2
, otherwise, nobody can help you.
What a stupid bot comment! First I did provide the debug output Second the claim is that the usual upgrade is meaningless in the dockerized approach
In my view:
docker pull neilpang/acme.sh
don't use the latest
tag, it always tries to upgrade.
please use a specified version instead:
docker pull neilpang/acme.sh:3.0.9
The specific tag version should always keep the version not upgraded.
Steps to reproduce
I am running the dockerized version of acme.sh with a cron entry like recommended in https://github.com/acmesh-official/acme.sh/wiki/Run-acme.sh-in-docker:
/usr/bin/docker run --rm -i -v /home/xxx/.acme.sh:/acme.sh --net=host neilpang/acme.sh --cron 2>&1 | /usr/local/bin/mailx -s Letsencrypt ...
obviously when there is a new version I get a report like:
This obviously updates the acme.sh code within the active container. However it is useless as the container is started with
--rm
and it breaks the container concept. So the next day I get again the old version:While I wonder what the "upgrade success tells me, the real upgrade procedure should pull the new docker image.
Of course the container content can be updated every day, but this is a waste of traffic and it obviously does not work.
Debug log
after deleting the latest image (here 3.09) and retagging the old one (here 3.08) as "latest", I get