I can’t find much about how boot2docker persistence works, i.e. how
/var/lib/docker is saved? I gather
/etc/rc.d/automount sets thing up but I’m not familiar enough with many of those commands to figure out what’s going on. My rough reading is that if it finds a volume labeled
boot2docker-data, it uses this, possibly formatting it if necessary? If running boot2docker inside VirtualBox, this means this volume is a Virtual Harddrive right?
Ultimately what I’m after is if it’s possible to switch things so
/var/lib/docker is actually a mounted VirtualBox shared folder. I’ve tried doing this and I get errors that look like this:
$ docker pull busybox ... 8c2e06607696: Error pulling image (latest) from busybox, endpoint: https://registry-1.docker.io/v1/, Untar re-exec error: exit status 1: output: symlink busybox /bin/ash: read-only file system 8c2e06607696: Error pulling image (latest) from busybox, Untar re-exec error: exit status 1: output: symlink busybox /bin/ash: read-only file system
So is it possible to use a mounted Virtualbox shared folder for /var/lib/docker, or does this conflict in some way with how persistence is currently handled, or maybe its just not possible at all?