Simon Deziel

We've discovered #288 at the same time so maybe the 2 are connected somehow.

@tomponline hypothesized that `/mnt` remained mounted in the microceph's snap (see https://github.com/canonical/lxd/pull/12793#discussion_r1475158229) which would explain nicely why doing the `swapoff`/`umount` before installing the snap would side-step the issue.

> ### HOST system > > 12 core > 64GB ram > btrfs file systems Question to self: could it be due to the automatic setting of `size.state` that is...

I'm unable to reproduce on Noble with a **Ubuntu Noble VM**: ``` root@hardhat:~# uname -a Linux hardhat 6.8.0-35-generic #35-Ubuntu SMP PREEMPT_DYNAMIC Mon May 20 15:51:52 UTC 2024 x86_64 x86_64 x86_64...

Same behavior with `5.21/stable` using a Noble VM: ``` root@hardhat:~# lxc exec vu1 -- uptime 21:55:34 up 1 min, 0 user, load average: 0.13, 0.06, 0.02 root@hardhat:~# snap list lxd...

Sorry for the very long delay here, seems like "tomorrow" just happened ;) I tested with a Windows 11 VM backed by `btrfs` on LXD `5.21/stable` and it worked with...

> Maybe its a naive solution. Maybe it does not even work (I don't have that kind of hardware for testing ah). `tf-reserve hoodin` should get you such HW ;)

@JohnHammell I share the same concerns as Tom, using the `current` directory is risky so I reported it: https://bugs.launchpad.net/prometheus-snap/+bug/2066910 To your point of making our documented procedure work, I think...

@JohnHammell I meant to have `/var/snap/prometheus/current/tls/` be a symlink to `/var/snap/prometheus/common/tls/`. This way, when `current` is refreshed, only the symlink needs to be recreated. As for `current` already being a...

After creating the symlink to disable the runc profile, you also need to unload the profile for this to take effect: ``` # ln -s /etc/apparmor.d/runc /etc/apparmor.d/disable/ # apparmor_parser -R...