Daniel J Walsh

Should this issue be closed?

What are the permissions on the tmpfs on the second run?

First run ``` / $ ls -ld /tmpfs drwxrwxrwt 2 root root 40 Feb 18 14:00 /tmpfs ``` Second ``` / $ ls -ld /tmpfs drwxr-xr-x 2 root root 40...

I would guess that since the directory does not exists on the first run docker creates it and mounts the loose permissions on top. But the underlying directory gets created...

``` cd /var/lib/docker/devicemapper/mnt/d38b20c7143d58cf10a7d8c673ae9daf8689394d91bb8d4caa24425ae50d9c7f/rootfs/ # ls -ld tmpfs drwxr-xr-x. 2 root root 6 Feb 18 09:00 tmpfs ```

If you run this same test with /tmp or /var/tmp, I think it will work correctly.

Well it will work with any directory, the problem here is the directory did not exist in the image before running your command. Since the directory does not exist, there...

Actually option #1 is available now. ``` docker run --tmpfs /tmpfs:mode=1777 -ti fedora sh ``` Except it requires more thinking on the users part.

I wrote the code, but forgot that we pass the mount options after the ":" Part of my patch never got in though, so I might be opening a pull...

I have no problem with that other then it is potentially a breaking change.