Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Issue with AutoFS mounts and docker 1.11.2 #24303
Have issues with bind mounts of nfs volumes inside containers, and on the host. The mounts work fine when no container is present. If the bind mount into the container is successful then it seems to break the mounts on the host. Note: The mounts are controlled by autofs. More details below.
Additional environment details (AWS, VirtualBox, physical, etc.):
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
This has worked in previous versions of docker (client and server identical version numbers in all cases), including:
Additional information you deem important (e.g. issue happens only occasionally):
I'm still trying to narrow down the differences, but sometimes the mount errors are returned in the container, and sometimes their returned on the host. I thought that it may be related to the
I'm going to try and reproduce with
So interestingly... even with
Had the idea after reading this post about bind mounting autofs mounts elsewhere in the filesystem. Seems to have resolved the issue. I'm gonna roll back. I'm going to try again with the older version of autofs to confirm that that's where the issue was coming from. post back in a bit.
Just to be clear, the working problematic autofs version was:
and the working version:
okay.. so I was wrong. bumping the nfs version doesn't fix the problem. I'll go into more depth about how to recreate the problem....
So we have some autofs nfs mounts, which are mounted under nfs. If we create a container, which bind mounts the nfs folder
Now, if i leave the container, umount the drive on the underlying host, and then attempt to remount it, by performing an ls of the nfs mount, then i get the following error:
Note: I've tried this with
This is with the latest stable version of autofs from the CentOS repository. and the docker version in the top comment of this post. Any guidance on where to look next? This wasn't an issue in previous versions of docker, i've just rolled back to
That may well be an error from compose, perhaps it does not support shared
On 30 Aug 2016 11:04 a.m., "chrert" firstname.lastname@example.org wrote:
what if we do not use autonfs?how about just use the normal nfs?