-
Notifications
You must be signed in to change notification settings - Fork 27
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
Update to certbot 0.22.2 #40
Comments
Hello viict, yes, I plan to upgrade this to allow wildcard certificates. |
Any news regarding update ? This will be really handy ;) |
Sorry for being so silent. Have a lot to do with my indie gaming startup. And I need to think about missing additions like adding certs during runtime, using docker config or secrets. I will try to find some time this month. |
Hey. I've had to build my own image of this as your image has been broken since certbot/certbot#5856 Which was fixed by certbot/certbot#5941 I'm sure everyone else would be happy if you rebuild the image with the latest Certbot bugfixes :) |
@freshollie did you just rebuild the image using the provided Dockerfile? Were any other changes necessary? |
@japsen rebuilding the image downloaded the latest certbot. You can use |
@freshollie Thank you! |
@freshollie what about a PR? |
Hello there. I just created a new tag. Docker Cloud should build a new version and release it under v0.1.6. This may take some minutes. Sorry this took so long :/ At last I now have two weeks holiday.... Cheers! edit Build is done. v0.1.6 uses certbot 0.26.1 - could you please check if this version works? Hopefully certbot-commands weren't changed. |
using the "latest" image I was seeing the following errors which seem to line up with the cases @freshollie reference. "DeserializationError: Deserialization error: Could not decode 'status' (u'ready'): Deserialization error: Status not recognized" after pinning to the 0.1.6 tag I no-longer see these errors. |
Hi,
Is there a planning to upgrade this to use the latest certbot?
The use wildcard certificates would be a nice feature to use with docker-flow.
The text was updated successfully, but these errors were encountered: