If you are using different containers for db and web, maybe ensure that the db container is started first and the startup of the web container is delayed to account for that?
Yes I call it “discourse” because it is running together with many other containers. Having it named just “app” feels like calling my girl friend something like - “girl friend” Install went well and it runs well too. Just the rebuild does fail. Should this be because I do not call it “app”?
I’m using CentOS 7 on the host because the host itself is an OpenVZ container. My tests with Ubuntu did not worked well so I went the CentOS road because that’s what OpenVZ supports best. So far no problems using this setup.
Digging into this a little more, the only viable practical options are
AUFS
overlayfs
Unfortunately, AUFS is not part of the kernel and will never be, overlayfs looks like it will make it into the kernel, but could be bleeding edge at the moment.
@sam is adding better protection for this in the bootstrap step – we really can’t proceed if the filesystem is not one that is known to be compatible with Docker. Too many support issues…