Next LXCFS release


(Dani) #1

Hello,

I just wanted to know when (an estimated date) the next LXCFS version will be released. We need two changes that were committed to master since the last tag.

Thanks in advance. Regards,

Dani


(Stéphane Graber) #2

We should have a bugfix 3.0.4 soon-ish once we’re done dealing with some other releases (LXD 3.11, LXC 2.0.11) and have a bit of time to cleanup any cherry-pick backlog.

That’s assuming that what you’re waiting for isn’t a new features as we don’t backport those to stable releases.


(Dani) #3

Hi Stephane,

Thanks for your reply. What you mean is that the two following commits https://github.com/lxc/lxcfs/commit/45bf5f3cab821a32e40020315fcd0e0ab4fcf13f and https://github.com/lxc/lxcfs/commit/b04c86523b05f7b3229953d464e6a5feb385c64a won’t be added to the next release?

What is the risk of creating a new package from the master branch and use it on our systems? I mean, what is the release process? Other tests are done before releasing a new version? We have already created a new package from the master branch but we are not sure how safe it is to use.


(Stéphane Graber) #4

Indeed those two definitely aren’t bugfixes, so we may roll a LXCFS 3.1 feature release with them in but LXCFS 3.0.3 will not have them.

Rolling your own package should be fine, most of our testing happens organically as a bunch of us tend to run the current master code, others built their own and we do run the built-in testsuite but that’s about it.

LXCFS should be pretty safe to use in general, worse case it crashes and you need to unmount it or restart the containers to get back online. It’s read-only from the container’s point of view and doesn’t handle data itself so there’s no real concern about data loss or anything of the like with lxcfs.


(Dani) #5

Thank you so much


(Dani) #6

Hi Stephane,

The package that we created from master branch is printing out the following error:

lxcfs[3622]: bindings.c: 5485: refresh_load: Open proc_path failed in refresh_load.
lxcfs[3622]: bindings.c: 5485: refresh_load: Open proc_path failed in refresh_load.
lxcfs[3622]: bindings.c: 5485: refresh_load: Open proc_path failed in refresh_load.
lxcfs[3622]: bindings.c: 5485: refresh_load: Open proc_path failed in refresh_load.
lxcfs[3622]: bindings.c: 5485: refresh_load: Open proc_path failed in refresh_load.
lxcfs[3622]: bindings.c: 5485: refresh_load: Open proc_path failed in refresh_load.
lxcfs[3622]: bindings.c: 5485: refresh_load: Open proc_path failed in refresh_load.
lxcfs[3622]: bindings.c: 5485: refresh_load: Open proc_path failed in refresh_load.
lxcfs[3622]: bindings.c: 5485: refresh_load: Open proc_path failed in refresh_load.
lxcfs[3622]: bindings.c: 5485: refresh_load: Open proc_path failed in refresh_load.

Will have a glance at the code asap, but just in case you know what the problem is.

Thanks,

Dani


(Stéphane Graber) #7

This error suggests an issue finding the liblxc library on reload.

I’d suggest running strace against the lxcfs process to see exactly where it’s looking and why it’s not there.