Open olalonde opened 9 years ago
Well, I fixed the problem by mounting /Users with nfs instead of vboxsf in boot2docker. I made a script here: https://gist.github.com/olalonde/3f7512c0bd2bc8abb46d
@tianon @bfirsh another b2d user that created an nfs based solution....
Disclaimer: I just tested the script on my local machine so I'm not sure it will work on different setups. Basically the script adds the correct line to /etc/exports on OS X and executes a shell script on b2d VM to mount /Users with nfs. It's safe to run the script multiple times because it deletes any line in /etc/exports that start with /Users (a backup of /etc/exports is made on first run).
I just tried with docker for mac it works completely natively.
https://docs.docker.com/docker-for-mac/
I was able to use a blockchain that I copied from my bitcoind node that I was running in docker-machine.
I have a docker-compose.yml file that looks like this:
I'm getting the following error when running
docker-compose up bitcoind
:After some Googling, this is probably because LevelDB doesn't support the vboxfs filesystem which boot2docker uses for mounted directories.
I was wondering what are my options here (considering I want to persist the bitcoind data across
docker-compose up
commands). I tried mounting a directory directly from the boot2docker VM and it works fine but the VM quickly runs out of space (and resizing it is a PITA). Ideally, I would like to mount the~/.bitcoind
from my host but it won't work with vboxfs.Is there a way to change which filesystem boot2docker uses for mounting?