Update to certbot 0.22.2

[viict]

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.

[hamburml]

Hello viict,

yes, I plan to upgrade this to allow wildcard certificates.

[nohaapav]

Any news regarding update ? This will be really handy ;)

[hamburml]

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.

[freshollie]

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 :)

[japsen]

@freshollie did you just rebuild the image using the provided Dockerfile? Were any other changes necessary?

[freshollie]

@japsen rebuilding the image downloaded the latest certbot. You can use freshollie/docker-flow-letsencrypt if you don't want to do this yourself.

[japsen]

@freshollie Thank you!

[drozzy]

@freshollie what about a PR?

[freshollie]

@drozzy there is no PR. @hamburml merely needs to rebuild the docker image with the latest version of certbot.

[hamburml]

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.

[LelandSindt]

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.