Thanks for filing this bug in Ubuntu.
I don't think it's safe for the service to just simply nuke the contents
of /var/lib/lxcfs prior to mounting/starting.
It does sound like a local configuration problem, or maybe a bug that
existed in 17.04 (which is what you first installed). It will be hard to
reproduce now if it depends on 17.04, as that release is end-of-life.
In your case, since the contents are cgroup and proc with the fuse
system NOT MOUNTED (please make sure), you can delete those and then
restart the service.
Something like this:
sudo systemctl stop lxcfs.service
# confirm with mount that it is unmounted
mount -t fuse.lxcfs
# delete or move away the contents of /var/lib/lxcfs, your choice
# start the service
sudo systemctl start lxcfs.service
# confirm it's mounted
mount -t fuse.lxcfs
If you come across a way to reproduce the problem from the beginning, like a
fresh install, or an upgrade from a previous release of ubuntu, then please
update this bug. In the meantime, I'll mark it as incomplete.
** Changed in: lxcfs (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756785
Title:
lxcfs startup failues because fuse directory not empty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1756785/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
