Ok, so the mount table output confirms that your LXD default storage pool isn't visible in the host's mount table, so that's not what's triggering nautilus.
Also, if that was the case, I'd have seen it on my own machine a long time ago ;) My best guess is that it's the loop device (also called default.img) which nautilus is incorrectly showing as some kind of external block device (like a USB stick or SD card). You'll most likely see it in `losetup -a` and it may show up in some `/dev/disk/` sub-directories which I supposed nautilus or something in the gnome desktop is monitoring. Unfortunately unlike actual mount entries that we can hide in a different mount namespace or pass custom mount flags to have the desktop ignore, the same can't be done with block devices, so re-assigning this to nautilus for further investigation. ** Package changed: lxc (Ubuntu) => nautilus (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1915091 Title: Nautilus shows LXD storage pool in sidebar Status in nautilus package in Ubuntu: Incomplete Bug description: I recently set up LXD 4.11 on Ubuntu 20.04 with a file-backed btrfs storage pool called "default". Now Nautilus shows a "default" device in the sidebar despite the loop device not being intended for users to directly interact with. System: Ubuntu 20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1915091/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
