Stéphane Graber
Stéphane Graber
The second `ldd` should be against `liblxcfs.so` not `libfuse.so`
Most likely `htop` is using `sysinfo` or a similar syscall which lxcfs cannot emulate. `lxcfs` can only replace files, if something is getting the information through other means, there's nothing...
Can you show `cat /proc/meminfo` from inside the container?
@brauner do you see anything wrong above which could explain why htop is getting such an incorrect value?
Oh, that'd be problematic :) Can you try `mount -t tmpfs tmpfs /proc/spl` and see if the problem goes away then?
Hmm, okay, then I think we need a bug report against `htop` as it seems like it's being slightly too smart for its own good on this one :)
@brauner I can't think of a good reason to disable this one. If someone comes up with a good reason to turn it off, I think I'd prefer we switch...
> I'm just a bit concerned that we're too lax with new features here and might introduce regressions. That's the main driver for me requesting this. Well, this isn't going...
LXCFS is a FUSE filesystem, so to run it, you need access to FUSE (/dev/fuse and /sys/fs/fuse/connections). Then when running LXCFS, the target path will be populated with files that...