Anurag Priyam
Anurag Priyam
That's helpful, thanks. I will keep you posted. For now, I must add that the timeout / unresponsive terminal I am experiencing is after a few minutes of inactivity.
Only if you delete the bells-and-whistles image oswitch created and run again. Should this be the default behaviour? Probably yes. The current behaviour is a leftover from when I switched...
Consider using docker to get into the image to debug things while I fix this issue? The image oswitch created will be listed in `docker images` as "oswitch_*_qiime".
oswitch could detect the failure that and try with a new UID, but I don't know how will filesystem permissions work with a different UID. And why is UID 1000...
`/Volumes` is never mounted. Nor `/Volumes/Macintosh HD`. If you have anything else in `/Volumes`, it should be mounted under `/Volumes` in the container.
Why would you want access to `/Applications` or `/Library` in the container? I will have to check if root owned files / dirs can be mounted `rw` within container. Did...
I made the necessary changes in switch, but still unable to mount `/Applications`. Probably because boot2docker is getting in the way. Perhaps @bmpvieira can help.
Test case is simple: `docker run -it -v /Applications:/Applications`. `/Applications` in the container comes up empty.
It is indeed `boot2docker` getting in the way. On Mac, `boot2docker` is the _real_ host, not OSX. The workaround is as below, using `/Applications` dir as an example: ``` boot2docker...