-
-
Notifications
You must be signed in to change notification settings - Fork 5k
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
upgrades in dockerized acme.sh not working #5303
Comments
Please upgrade to the latest code and try again first. Maybe it's already fixed. |
What a stupid bot comment! In my view:
|
don't use the
The specific tag version should always keep the version not upgraded. |
Why don't you just use Watchtower? So I have never had any problems updating and am always on the latest version. Watchtower has been reliably updating my containers for years. In the case of a container update, the container and the image must be replaced. A task in the container will not work in the long term. |
@nillebor @Neilpang |
That's right. Your Thread is: upgrades in dockerized acme.sh not working and you wrote I am running the dockerized version of acme.sh. The lattest Image is from yesterday https://hub.docker.com/r/neilpang/acme.sh. all scripts are up-to-date in it. Please use the latest (stable) version or the dev version to get the current code. Version 3.0.9 has not been updated for 3 weeks. |
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
The text was updated successfully, but these errors were encountered: