Closed ghost closed 2 years ago
How I solved it in a bruteforce way:
After that, docker could not start the container.
Luckily I had nothing too important there, so I ran
docker system prune
But I will have to set up the data in a db again.
It does worry me though about how to restore a snapshot in the future.
After this I changed the docker storage driver to fuse-overlayfs
instead of btrfs
by following https://docs.docker.com/storage/storagedriver/overlayfs-driver/
So that this issue will not occur in the future.
Hi @Deckweiss
Thanks for reporting :)
You are right, that problem is more a layout problem than a ButterManager issue 'per se'. Some time ago, I created a cheatsheet and documentation regarding to a simple BTRFS layout for a new system and you can see here this is something I pointed it out, because it is a real problem for people that use Docker in a BTRFS filesystem.
So your solution is the easiest one I found too: If you are running Docker in a BTRFS filesystem, the best option is to change the configuration of the storage driver that Docker will use by default. Otherwise, some problems could arise sooner or later as you mentioned in this issue.
Best wishes!
When trying to restore the previous snapshot I get
I think this is due to docker using btrfs storage driver when your system is btrfs. https://docs.docker.com/storage/storagedriver/btrfs-driver/
btrfs-list
btrfs subvolume list /mnt/defvol/_active/root/var/lib/docker/btrfs/
This is such a mess ... not sure if buttermanager can really do much about that.