Improve Azure File Share support

[vrepetskyi]

Improve Azure File Share support

[vrepetskyi]

Thank you for your fast response.

Here's the solution I came up with in the meantime. Because the container's IP address is assigned upon its creation, I automated the DNS record update as well. My scripts deploy FastAPI to Azure, point Route 53 to it, and start your service next. The keys are successfully stored on a separate File Share volume.

The solution isn't perfect, but someone may find it helpful.

[JonasAlfredsson]

Hi vrepetskyi,

Makes me happy you find the service useful :)

Yes, certbot uses symlinks in order to not keep multiple copies of the certificates, and it appears like others have run into similar issues as you:

• certbot/certbot#7880
• https://community.letsencrypt.org/t/why-does-certbot-use-symbolic-links-do-certain-paramaters-overide-this-behaviour/27966/12

Your solution seems to be the one suggested in the first thread, and since I do not use Azure I don't really have any solid suggestions for you here.
However, unless you recreate the container often you could probably get away with not mounting this volume. That would just lead to a little bit longer startup time in case the container needs to be recreated.