This ZFS bug exist in LXD for so long and it is becoming harder to use on production . We have to reboot whole server just to start a container. That is totally killing the purpose of using LXD .
This bug happens frequently and we need to come up as a community to resolve this.
Unless this is fixed , LXD shouldn’t be considered Production Ready.
There are many issues regarding this on the lxd github but main Devs couldn’t able to come up with a proper solution yet.
- One theory is it is due to
snapbuilds , the distro build is fine ( AFAIR , i cannot find the thread @stgraber mentioned about that ).
- It was definately due to ZFS ? Then should we stop using it?
- 4.20 have fixes by @tomp trying to resolve this by not using
zfs mount, which seems to work for some but dosen’t work for me .
I love LXD , it make me able to avoid Kubernetes’ complexity , and i am using LXD + PyLXD in a product , as a core feature / lib to provide multiple classrooms to improvished area , to give online education, which is going to launch in a week.
But if this happen during production , i will have a lot of trouble.
So what can we do to avoid this?
- Provide official Debian Packages?
- Use Btrfs instead of ZFS ?
- or Stop using ZFS as default?
Error: Failed preparing container for start: Failed to run: zfs set mountpoint=none canmount=noauto default/containers/magento-dev: umount: /var/snap/lxd/common/shmounts/storage-pools/default/containers/magento-dev: no mount point specified. cannot unmount '/var/snap/lxd/common/shmounts/storage-pools/default/containers/magento-dev': umount failed Try `lxc info --show-log magento-dev` for more info