Created attachment 649016 [details] log output After trying to start lxcfs manually, turns out it wasn't able to start or restart, two problems. First, the directory /var/lib/lxcfs didn't exist, so it couldn't use it as a mount point. I just did a mkdir as root, and it didn't seem to have a problem with ownership, but I don't know if there should be any modifications there. Next, during attempt to restart, it tried to user /bin/fusermount rather than /usr/bin/fusermount. I added the /usr to the service file. I tried to remove the mount point to test, but it couldn't unmount the fs from that mount point when it didn't exist, but at least the binary seemed to do the error reporting, so I guess that is as close as I'll get without another error.
Hmm yeah, with openrc a lot of these happen via the init.d script, https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-fs/lxcfs/files/lxcfs-4.0.0.initd I tried putting them to the ebuild initially but that proved to be flaky. I'll need to study systemd to replicate the init.d behaviour there...
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cbde434758c938aa1452aa31818fcb3b8fd73245 commit cbde434758c938aa1452aa31818fcb3b8fd73245 Author: Joonas Niilola <juippis@gentoo.org> AuthorDate: 2020-07-13 06:17:59 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2020-07-13 07:15:59 +0000 sys-fs/lxcfs: systemd related fixes, #732364 Closes: https://bugs.gentoo.org/732364 Signed-off-by: Joonas Niilola <juippis@gentoo.org> sys-fs/lxcfs/files/lxcfs-4.0.0.service | 18 ++++++++++++++++++ .../{lxcfs-4.0.4-r1.ebuild => lxcfs-4.0.4-r2.ebuild} | 2 +- 2 files changed, 19 insertions(+), 1 deletion(-)
