Created attachment 1294109 [details] log Description of problem: oc cluster up fails with --host-volumes-dir flag on Windows Version-Release number of selected component (if applicable): oc v3.6.131 kubernetes v1.6.1+5115d708d7 docker@openshift3:~$ docker version Client: Version: 1.13.1 API version: 1.26 Go version: go1.7.5 Git commit: 092cba3 Built: Wed Feb 8 08:47:51 2017 OS/Arch: linux/amd64 Server: Version: 1.13.1 API version: 1.26 (minimum version 1.12) Go version: go1.7.5 How reproducible: Always Steps to Reproduce: 1.Use docker-machine tool to create a docker-machine VM on Windows OS 2.Docker ssh docker-machine VM, create dir /tmp/volumes 3.Launch openshift cluster with --host-volumes-dir flag C:\Windows\system32>oc cluster up --image=brew-pulp.../openshift3/ose --version=v3.6 --host-volumes-dir=/tmp/volumes --docker-machine=openshift3.6 Actual results: FAIL Error: cannot create volumes dir share Caused By: Error: Docker run error rc=1 Details: Image: brew-pulp.../openshift3/ose:v3.6 Entrypoint: [/bin/bash] Command: [-c grep /tmp/volumes /rootfs/proc/1/mountinfo | grep shared || nsenter --mount=/rootfs/proc/1/ns/mnt mount --make-shared /tmp/volumes] Error Output: mount: /tmp/volumes: Invalid argument Expected results: Launch openshift cluster successfully Additional info:
This is expected, given the /tmp directory is a mounted tmpfs file system. In general, it is not recommended to specify --host-volumes-dir argument when running on Windows or Mac, but if you do use it, you need to make sure that the directory resides in the Docker VM and that you can create a shared mount at that location. If some other filesystem is already mounted, then cluster up won't be able to create the shared mount. I am lowering the severity of this bug. However, we do need to explain this better in the documentation.
Took a closer look and it seems that this will happen even if you're pointing to a directory where you can create a shared mount. It happens both on Mac and Windows. It should be fixed, but still keep it as a low severity bug since there's not much benefit in using the option in either platform.
This is no longer occurring in the latest origin master. An alternate volumes directory can be used. However, on Windows and the Mac this must be a directory inside the Docker vm and can't be a directory on the host machine, because creating a share for it will fail.
Verified $ ./oc version oc v3.7.0-0.158.0 kubernetes v1.7.6+a08f5eeb62
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0489