lots of directory cannot mount using autofs in docker container, maybe soft link???

[hanae2e]

Output of docker version:
i062683@mo-9dfe42e4f:> ls /sapmnt/production2/makeresults/
HANA HANA-write
i062683@mo-9dfe42e4f:> docker version

Client:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.6.1
 Git commit:   9e83765
 Built:
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.6.1
 Git commit:   9e83765
 Built:
 OS/Arch:      linux/amd64

Output of docker info:
i062683@mo-9dfe42e4f:~> cat /etc/issue

Welcome to SUSE Linux Enterprise Server 12  (x86_64) - Kernel \r (\l).

i062683@mo-9dfe42e4f:~> docker info

Containers: 2
 Running: 2
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.11.1
Storage Driver: devicemapper
 Pool Name: docker-8:16-24297473-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 3.729 GB
 Data Space Total: 107.4 GB
 Data Space Available: 103.6 GB
 Metadata Space Used: 6.877 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.141 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Either use `--storage-opt dm.thinpooldev` or use `--storage-opt dm.no_warn_on_loop_devices=true` to suppress this warning.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.03.01 (2016-01-25)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 3.12.55-52.42-default
Operating System: SUSE Linux Enterprise Server 12
OSType: linux
Architecture: x86_64
CPUs: 10
Total Memory: 124.2 GiB
Name: mo-9dfe42e4f
ID: MOQU:MDOJ:CXYW:OMRL:JNYX:GFKO:GSKI:HYNY:YGMW:CTH3:SE3Z:ST66
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
WARNING: No kernel memory limit support

Additional environment details (AWS, VirtualBox, physical, etc.):

i062683@mo-9dfe42e4f:~> cat /etc/issue

Welcome to SUSE Linux Enterprise Server 12 (x86_64) - Kernel \r (\l).

Steps to reproduce the issue:

1. autofs install
2. mount files

Describe the results you received:

i062683@mo-9dfe42e4f:~> docker exec -ti node11 bash
node11:/ # ls /sapmnt/production2/
naas
node11:/

Describe the results you expected:

i062683@mo-9dfe42e4f:~> ls /sapmnt/production2
commonrepo  components  contexts  dev  makeresults  misc  naas  test  units  weekstone
**Additional information you deem important (e.g. issue happens only occasionally):**

[thaJeztah]

How did you start the container you're exec-ing into? Also note that I think this may be a duplicate of #13700

[hanae2e]

A little difference with 13700, autofs does work in container, just docker exec -it user bash as normal, but here, autofs cannot mount all of the directory, there are only part of them, so i think the directory with soft link may not mount correctly.

[thaJeztah]

Can you provide a minimum example to reproduce the issue? Your error description, for example, doesn't show how you start the container, and it would be helpful to have the (as simple as possible) steps to reproduce

[hanae2e]

suse 12.1, docker 1.11.1

1. docker run -d --privileged=true --name=%s --hostname=%s -v %s:/HANALocal -v /hana --add-host qadb:10.68.91.245 -p 22 %s /usr/sbin/sshd -D

2. in docker container.
   zypper in autofs

   using autofs to do mount point operation.
   step 1: update auto.master step 2: generate mount.map file step 3: update the map file mount.area51.map step 4: update domain resolution search path step5:aumount, to start autofs, not service autofs start. sorry cannot offer more command info, its in company confidential.

   with this operation, i find only some directory can found in container, not all, so I paste the info here.

[hanae2e]

hello ,

is it the same issue with 1676???? docker container does not allow soft link in container????

thanks,

[thaJeztah]

@hanae2e which issue is that? looks like you mentioned the wrong number

[sam-thibault]

This is an old issue. I will close it as stale.