Results 49 comments of Devon Schwartz

I am with annoprac. We believe we have a solution to this, but we do not know how to test. How do we use Jenkins and test lxc-top/ lxc-create on...

![Screenshot from 2024-04-29 12-49-30](https://github.com/lxc/lxc/assets/41024725/77a7030c-daaa-40c9-ad79-a1a5ad09fb28) Also on ubuntu images

![Screenshot from 2024-04-29 13-44-23](https://github.com/lxc/lxc/assets/41024725/3e2f0f79-748f-4c54-aa2f-dd2bdc58416d) This is the error we get running ./lxc-create from the main branch after building the repo.

[ ![Screenshot from 2024-04-29 16-21-06](https://github.com/lxc/lxc/assets/41024725/f4a60bb0-b168-493e-b1a9-b6c856b53ee0) ](url) We have the same issue with parse config file. We made sure to run sudo make install and sudo make all

![Screenshot from 2024-04-29 17-03-09](https://github.com/lxc/lxc/assets/41024725/c811a443-6b7a-42ff-bb13-7c047f9e16ac) Apparently the capability passed through is "mac-admin" is this correct? When I pass in "none" that creates a valid container, but then lxc-start will have issues.

> Make sure you have libcap-dev libseccomp-dev libcap-ng-dev libapparmor-dev for most features to be enabled. Now we have valid capabilities, but we still fail to parse the config file ![Screenshot...

We noticed that print and ERROR statements in do_lxcapi_get_cgroup_item() do not make it to the terminal. Is this expected behavior?

We were able to get printing to work in do_lxcapi_get_cgroup_item(), and we traced the issue to open_at() inside of lxc_read_try_buf_at() in src/lxc/file_utils.c. The path or file descriptor that's passed in...

> It's a valid path for cgroup1 but not for cgroup2. > > Under cgroup2, the equivalent is `memory.current` (you can look those up in /sys/fs/cgroup/lxc.payload.NAME/`) Does this also apply...

How do we know which c-group the system is using?