After freshly installing Ubuntu 18 I am receiving the following error when trying to launch a docker container that has a bind to a LVM (ext4) partition:
mkdir /storage: read-only file system
I have tried reinstalling the OS, reinstalling Docker and forcing the drive to mount as RW (everything that isn't docker can write to the drive).
The directory that is being bound is currently set to 777 permissions.
There seems to be almost no information available for this error.
Try removing docker from snap and reinstalling it following the official docker steps.
Remove docker from snap:
snap remove docker
Then remove the docker directory and the old version:
rm -R /var/lib/docker
sudo apt-get remove docker docker-engine docker.io
Install official docker: https://docs.docker.com/install/linux/docker-ce/ubuntu/
docker run hello-world is working. ;) ...probably because it does not use volumes (this is of course a disappointing situation)
docker build, docker save and docker load need to be in $HOME."Update 01/2021: while still pretty cool, Snaps don't always work. Specifically with the Docker Snap, it didn't work for Swarm mode, so I ditched it and installed Docker the recommended way.
Snaps are actually pretty cool, IMO, and think it's beneficial to run Docker within a Snap than installing it directly on the system. The fact that you're getting a read-only permissions error is a good thing. It means that a rogue container isn't able to wreak havoc on your base OS. That said, how to fix your issue.
The reason that this is coming up is that Snaps will expose the host OS as read-only so that Docker can see the host's files, but not modify them (hence the permission denied error). But there is a directory that the Docker Snap can write to: Actually, a better directory that snap can write to is /var/snap/docker./home. I created /home/docker for containers to have persistent storage from the host system.
In your case, you wanted /storage to be writable by Docker containers. I had a very similar use-case, which led me to this SO post. I solved this by mounting my storage within the docker snap directory /home/docker; the easiest example simply being a directory on the same filesystem:
mkdir -p /home/docker/<container name>/data
In my case, I created a ZFS dataset at the location above instead of simply mkdir'ing a directory.
Then, the container I ran could write to that with something like:
docker run -ti -v /home/docker/<container name>/data:/data [...]
Now you have the best of both worlds: Docker running in a contained Snap environment and persistent storage. 🙌🏽
if you have currently have this problem on Windows with Docker Desktop, try downgrading to Docker Desktop version 4.24.2:
If you're working with output files that you're saving to your file system using bind mounts, it's important to be careful about the path you're using.
Ensure that the path has the proper permissions. For example, avoid using root paths unless absolutely necessary.
It's generally safer to use a relative path from your execution directory. If you must use a root path, make sure it is accessible and has write permissions to avoid issues when saving files.
Simple Example:
docker run -v "$(shell pwd):/src" image-xxx some-cmd --output=./somedir
you can create/run your container with --privileged:
ex.:
docker run --privileged -i --name master --hostname k8s-master -d ubuntu:20.04
read-only file systemmight indicate hdd failure. Happened to me, changed hdd and everything worked.