Expected behavior I expect to be able to access /Mac in my containers, per the docs. Actual behavior I don’t see any /Mac mount point. If I connect to the Moby VM then I see what appears to be an error related to the mount: docker:~# df Filesystem 1K-blocks Used Available Use% Moun…

I’m being prompted to log in after that screen command – any thoughts? [Login Prompt] I’ve uploaded my logs, bugsnag id is: 4D76F500-A6CA-45D2-B18A-ABFFBF17071E

Thanks! docker:~# cat /var/transfused_start.log 2016-03-29 20:12:11.250 mount /bin/fusermount -o allow_other,max_read=32741,subtype=osxfs /Mac 2016-03-29 20:12:11.251 Log mount trigger fired on /Mac, logging to /Mac/Users/tom/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/l…

Providing my info as well: ~ pinata diagnose -u OS X: version 10.11.4 (build: 15E64a) Docker.app: version v1.11.0-beta6 Running diagnostic tests: [OK] docker-cli [OK] Moby booted [OK] driver.amd64-linux [OK] vmnetd [OK] osxfs [OK] db [OK] slirp [OK] menubar […

[image] ddunbar: df: /Mac: Socket not connected Can anyone comment on how to get more info on the “Socket not connected” message?

@cliffom I have the same results to all your tests on my machine. Good catch! So osxfs is there, it’s just not automounting. What’s more, this confirms that the test from the file access performance thread was, in fact, running over osxfs; and so that’s where the speed issue is. @ddunbar df for me …

@tomfrost I don’t think auto-mounting /Mac to containers is intended behavior. Containers only mount volumes passed explicitly with -v; Having /Mac in the VM allows you to mount directories outside of /Users and in the Mac volume root / by prefixing them with /Mac. At least that is my understanding. …

That was my understanding as well.

@ddunbar Socket not connected is concerning to me – it indicates that the VM-side component of osxfs is not running. Can you reproduce it? Does it occur on start-up or only after running a container? Always after running a single container? Do you have a core file in / or /var?

@cliffom I believe your understanding is correct. We are still developing the appropriate bind mount semantics but, in Beta 6, the special host paths available for bind mounts are /Mac (the whole host), /Users, /Volumes, /tmp, and /private. The mount points only appear in containers when using -v to…

Unable to access volumes using osxfs ("/Mac: Socket not connected") - [f]stat[v]fs family of functions

Docker Desktop

dsheets (David Sheets) April 21, 2016, 9:07am 24

Hi Daniel,

Could you please try this again with Beta 8? If it still doesn’t work for you, posting the unique ID from pinata diagnose -u would be helpful as Beta 8 has both better file sharing robustness and better logging to help us track down this issue.

Thank you!

Elasticsearch 1.7.0 fails to start on docker4mac 1.11.1-beta10

Topic		Replies	Views
Crash when running container with host mount Docker Desktop beta	21	14123	September 30, 2016
Docker beta on mac fails to start Docker Desktop	27	13144	August 17, 2016
Df command inconsistent Docker Desktop	2	1855	April 14, 2016
Error running docker immediately after installing docker for Mac Docker Desktop	4	2552	August 17, 2016
Docker for mac won't start Docker Desktop macos	21	22079	September 16, 2022

Unable to access volumes using osxfs ("/Mac: Socket not connected") - [f]stat[v]fs family of functions

Related topics