Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Unable to read a symlink in a mounted volume from inside a Windows Container #28401
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Additional environment details (AWS, VirtualBox, physical, etc.):
Symlinks are used to enable atomic updates of secrets inside the containers. The directory containing secrets on the host (default:
This won`t be probably useful for your needs but you can create SymLink from the container itself. You just need to place the symlink into another folder (one that wasn`t mounted).
The changes propagate correctly in both directions.
After a few tries, I found my problem solved, seems it's more like a docker config issue for me, e.g.
The volume mount failed in the container, it reports error: the parameter is incorrect. It's still quite confusing, not sure why.
If I change mapping to drive, like below, it succeeded, it's quite confusing for me. Anyway, mounting to a drive in container should succeed.
So I arrived here from this page https://kubernetes.io/docs/getting-started-guides/windows/ having attempted to mount both a secret and azurefile volume without success.
Just to be absolutely clear. Do volumemounts simply not work for windows based containers/pods in Kubernetes running on Azure Container Services?
referenced this issue
Sep 26, 2017
Please note that:
You could find more details in below link: