Allow customisation of Azure File CIFS mount options within container instance (e.g., mfsymlinks)
When a Docker image is started with a linked Azure Files volume, a CIFS mount is created with a set of options however it is not possible to change or add new options to the mount config.
Reason: A community image I'm trying to use (an nginx proxy that deals with letsencrypt) expects to create symlinks within the mounted storage, but fails because the "mfsymlinks" option is not set which causes an error.
Resolution: Allow a way to customise the mount options, and/or enable 'mfsymlinks' by default.
More info on this issue and workarounds people are trying:
Yaroslav Admin commented
I have the same use case as Jason, where I want to use Let's Encrypt inside a container to generate an SSL certificate for my application and I want to store it as Azure Files volume to avoid re-generating after every container restart. This scenario is currently not possible, because certbot (tool to generate certificates) needs to generate symlinks. Please add possibility to customise mount options.
Since it's a docker feature, I'm pretty sure this is just a matter of exposing some settings just like the mountOptions in AKS. I'm checking the docs regularly hoping it will be resolved, but no luck.