AFAIK, /snap being busy in an lxd container is expected, as /snap
appears to be a bind mount:
root@purgefail:~# findmnt /snap
TARGET SOURCE
FSTYPE OPTIONS
/snap
/dev/sda1[/var/snap/lxd/common/lxd/storage-pools/default/containers/purgefail/rootfs/snap]
ext4 rw,relatime
Perhaps the lxd can comment on whether this can be addressed. In any
case it's a separate issue.
As for the problem with Bionic, I cannot reproduce that locally, in GCP
or as part the snapd CI. Please confirm that there are no snap
applications running (eg. snap-store), and that your shell is not
somewhere under /snap. Try running `lsof |grep ' /snap'` to check for
any processes.
** Also affects: lxd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: snapd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903967
Title:
Can't purge snapd: rm: cannot remove '/snap': Device or resource busy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1903967/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
