permission/ownership on directory issue when using trusted docker build in boot2docker

[jstrachan]

We've a trusted build
https://registry.hub.docker.com/u/fabric8/fabric8/

which works fine on linux and works fine if its built locally on OS X with boot2docker. However when pulled from the trusted build on boot2docker it has a permission issue. e.g. on my machine

docker pull fabric8/fabric8
docker run -Pit fabric8/fabric8 /bin/bash
fabric8@ac5d4f4d9c33:/opt/fabric8-karaf-1.2.0.Beta3$ ls -al
total 108
drwxr-xr-x 19 root    root     4096 Sep  8 08:10 .
drwxr-xr-x 14 root    root     4096 Sep  8 08:10 ..
drwxr-xr-x  2 fabric8 fabric8  4096 Sep  8 07:46 bin
drwxrwxr-x  3 fabric8 fabric8  4096 Sep  7 14:58 data
drwxrwxr-x  2 fabric8 fabric8  4096 Sep  8 07:46 deploy
...

The directory /opt/fabric8-karaf-1.2.0.Beta3 should be owned by fabric8:fabric8 and be writeable as we've done lots of chown / chmods in the docker file:

• https://github.com/fabric8io/fabric8-docker/blob/master/Dockerfile#L13
• https://github.com/fabric8io/fabric8-docker/blob/master/Dockerfile#L21
• https://github.com/fabric8io/fabric8-docker/blob/master/Dockerfile#L24

and so far have not figured out a work around to make this folder either writeable or owned by fabric8:fabric8.

It works fine on linux; just not on OS X with boot2docker.

Here's the version of my laptop

Client version: 1.2.0
Client API version: 1.14
Go version (client): go1.3.1
Git commit (client): fa7b24f
OS/Arch (client): darwin/amd64
Server version: 1.2.0
Server API version: 1.14
Go version (server): go1.3.1
Git commit (server): fa7b24f

I've installed VirtualBox 4.3.14-95030 along with boot2docker 1.2.0.

a colleague doesn't have this issue when using a linux box with these versions:

Client version: 1.2.0
Client API version: 1.14
Go version (client): go1.2.2
Git commit (client): fa7b24f/1.2.0
OS/Arch (client): linux/amd64
Server version: 1.2.0
Server API version: 1.14
Go version (server): go1.2.2
Git commit (server): fa7b24f/1.2.0

Am kinda out of ideas what can be causing this - anyone got any ideas to try figure out the issue?

Here's the background issue that prompted this issue: fabric8io/fabric8-docker#11