You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[rootless] driver "btrfs" failed to remove root filesystem: Failed to destroy btrfs snapshot /home/<USER>/.local/share/docker/btrfs/subvolumes for <ID>: operation not permitted #41762
Create the ~/.config/docker/daemon.json with the following content and run systemctl --user restart docker
{"storage-driver": "fuse-overlayfs"}
Description
btrfs driver is not really expected to be supported for rootless, but it is automatically chosen by default when the host filesystem is btrfs (e.g. on Fedora 33 Workstation), and it does not work actually.
Make sure docker info shows btrfs as the storage driver
docker run --rm busybox true
Describe the results you received:
$ docker run --rm busybox trueERRO[0000] Error waiting for container: container 17f95f5c7b026d9af2367b3676382ec1cc9c7c36e61e93ade87c30f86ce6ace1: driver "btrfs" failed to remove root filesystem: Failed to destroy btrfs snapshot /home/suda/.local/share/docker/btrfs/subvolumes for a9644718eaa311671fddd7440b275f97ad3642e21397cc7bd02244d5c9b0e81d: operation not permitted
Describe the results you expected:
It should work with btrfs, or it should chose fuse-overlayfs, not btrfs.
The latter one is my expected behavior, but the former one might be more ideal.
Additional information you deem important (e.g. issue happens only occasionally):
Fedora 33 Server users are unlikely to be affected because it does not use btrfs by default
Output of docker version:
$ docker versionClient: Docker Engine - Community Version: 20.10.0 API version: 1.41 Go version: go1.13.15 Git commit: 7287ab3 Built: Tue Dec 8 19:00:39 2020 OS/Arch: linux/amd64 Context: default Experimental: trueServer: Docker Engine - Community Engine: Version: 20.10.0 API version: 1.41 (minimum version 1.12) Go version: go1.13.15 Git commit: eeddea2 Built: Tue Dec 8 18:58:12 2020 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.4.3 GitCommit: 269548fa27e0089a8b8278fc4fc781d7f65a939b runc: Version: 1.0.0-rc92 GitCommit: ff819c7e9184c13b7c2607fe6c30ae19403a7aff docker-init: Version: 0.19.0 GitCommit: de40ad0
Workaround
Create the
~/.config/docker/daemon.jsonwith the following content and runsystemctl --user restart docker{"storage-driver": "fuse-overlayfs"}Description
btrfs driver is not really expected to be supported for rootless, but it is automatically chosen by default when the host filesystem is btrfs (e.g. on Fedora 33 Workstation), and it does not work actually.
Steps to reproduce the issue:
sudo dnf install -y policycoreutils-python-utils && sudo semanage permissive -a iptables_tdocker-rootless-setuptool.sh installexport DOCKER_HOST=$XDG_RUNTIME_DIR/docker.sockdocker infoshows btrfs as the storage driverdocker run --rm busybox trueDescribe the results you received:
Describe the results you expected:
It should work with btrfs, or it should chose fuse-overlayfs, not btrfs.
The latter one is my expected behavior, but the former one might be more ideal.
Additional information you deem important (e.g. issue happens only occasionally):
Fedora 33 Server users are unlikely to be affected because it does not use btrfs by default
Output of
docker version:Output of
docker info: