Hello Lawrence, Lawrence Jones: > 2. Start container, and attempt to mount the /image loop device > > root@39d1cc6bc2d0:/# mkdir /data > root@39d1cc6bc2d0:/# mount /image /data > mount: block device /image is write-protected, mounting read-only > > What I suspect is happening here (though I have no idea if this is correct) > is that the /image file has been created as part of the aufs filesystem, with > a file that represents it located in the hosts > /var/lib/docker/aufs/diff/<diff>/image.
Then I'd suggest you to confirm where "image" file is placed actually, as a 1st step. Then - How are your branches(layers) constructed? - Which branch is RW? - Does "image" file locate on the RW branch? > I’ve got two questions that I think this mailing list is probably able > to answer: I am afraid not. Because your questions are about docker mainly instead of aufs. For me, at least, I am not a docker user and have less experience on it. J. R. Okajima ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
