LXCFS 3.1.2 has been released

News
,
21 
root@d1:~# ps aux | grep lxcfs
root      2874  0.0  0.0 458096  4672 ?        Ssl   2019   0:38 /usr/bin/lxcfs /var/lib/lxcfs/
root      3328  0.0  0.0 899380 13352 ?        Sl    2019  37:19 lxcfs /var/snap/lxd/common/var/lib/lxcfs -p /var/snap/lxd/common/lxcfs.pid

root@d1:~# apt remove lxcfs
...
Removing lxcfs (3.0.3-0ubuntu1~18.04.1) ...

root@d1:~# systemctl reload snap.lxd.daemon
root@d1:~# lxc exec c99 uptime ; uptime
 10:09:34 up 37 days, 14:30,  0 users,  load average: 1.79, 1.87, 1.89
 13:09:34 up 37 days, 14:30,  2 users,  load average: 1.79, 1.87, 1.89

root@d1:~# ps aux | grep lxcfs
root      3328  0.0  0.0 899380 13356 ?        Sl    2019  37:19 lxcfs /var/snap/lxd/common/var/lib/lxcfs -p /var/snap/lxd/common/lxcfs.pid
22

Right, lxcfs will not usually ever be restarted as doing so breaks all running containers.

You could stop all your containers, kill lxcfs and then reload the snap, that should cause it to be brought back up, this time respecting your config.

23

Thanks, now it’s working!

root@d1:~# lxc exec c99 uptime ; uptime
 13:44:33 up 1 min,  0 users,  load average: 0.00, 0.00, 0.00
 16:44:33 up 10 min,  2 users,  load average: 3.32, 2.83, 1.56
24

Good day!
@stgraber any specific reason this is not default setup? May be it consumes some extra resources and thus avoided by default?

25

That’s exactly right, this causes a non-negligible added load on lxcfs as it requires tracking all processes and their state which isn’t something that lxcfs would normally do.

26

Clear, thanks!