Welcome to the Linux Foundation Forum!

Lab 3.2 privilege container cannot start

Trying to start the container as per the Lab privilege part fails with:

  1. lxc-start: priv-cont: lxccontainer.c: wait_on_daemonized_start: 877 Received container state "ABORTING" instead of "RUNNING"
  2.  
  3. lxc-start: priv-cont: tools/lxc_start.c: main: 306 The container failed to start
  4.  
  5. lxc-start: priv-cont: tools/lxc_start.c: main: 309 To get more details, run the container in foreground mode
  6.  
  7. lxc-start: priv-cont: tools/lxc_start.c: main: 311 Additional information can be obtained by setting the --logfile and --logpriority options

Here is the log:

  1. sudo cat privcont | grep ERROR
  2.  
  3. lxc-start priv-cont 20220524133445.257 ERROR cgfsng - cgroups/cgfsng.c:cg_legacy_set_data:2710 - No such file or directory - Failed to setup limits for the "devices" controller. The controller seems to be unused by "cgfsng" cgroup driver or not enabled on the cgroup hierarchy
  4.  
  5. lxc-start priv-cont 20220524133445.257 ERROR cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits_legacy:2777 - No such file or directory - Failed to set "devices.deny" to "a"
  6.  
  7. lxc-start priv-cont 20220524133445.257 ERROR start - start.c:lxc_spawn:1896 - Failed to setup legacy device cgroup controller limits
  8.  
  9. lxc-start priv-cont 20220524133445.257 ERROR lxccontainer - lxccontainer.c:wait_on_daemonized_start:877 - Received container state "ABORTING" instead of "RUNNING"
  10.  
  11. lxc-start priv-cont 20220524133445.257 ERROR lxc_start - tools/lxc_start.c:main:306 - The container failed to start
  12.  
  13. lxc-start priv-cont 20220524133445.257 ERROR lxc_start - tools/lxc_start.c:main:309 - To get more details, run the container in foreground mode
  14.  
  15. lxc-start priv-cont 20220524133445.257 ERROR lxc_start - tools/lxc_start.c:main:311 - Additional information can be obtained by setting the --logfile and --logpriority options
  16.  
  17. lxc-start priv-cont 20220524133445.258 ERROR start - start.c:__lxc_start:2074 - Failed to spawn container "priv-cont"
  18.  
  19. lxc-start priv-cont 20220524133658.619 ERROR cgfsng - cgroups/cgfsng.c:cg_legacy_set_data:2710 - No such file or directory - Failed to setup limits for the "devices" controller. The controller seems to be unused by "cgfsng" cgroup driver or not enabled on the cgroup hierarchy
  20.  
  21. lxc-start priv-cont 20220524133658.619 ERROR cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits_legacy:2777 - No such file or directory - Failed to set "devices.deny" to "a"
  22.  
  23. lxc-start priv-cont 20220524133658.619 ERROR start - start.c:lxc_spawn:1896 - Failed to setup legacy device cgroup controller limits
  24.  
  25. lxc-start priv-cont 20220524133658.619 ERROR lxccontainer - lxccontainer.c:wait_on_daemonized_start:877 - Received container state "ABORTING" instead of "RUNNING"
  26.  
  27. lxc-start priv-cont 20220524133658.619 ERROR lxc_start - tools/lxc_start.c:main:306 - The container failed to start
  28.  
  29. lxc-start priv-cont 20220524133658.619 ERROR lxc_start - tools/lxc_start.c:main:309 - To get more details, run the container in foreground mode
  30.  
  31. lxc-start priv-cont 20220524133658.619 ERROR lxc_start - tools/lxc_start.c:main:311 - Additional information can be obtained by setting the --logfile and --logpriority options
  32.  
  33. lxc-start priv-cont 20220524133658.619 ERROR start - start.c:__lxc_start:2074 - Failed to spawn container "priv-cont"
  34.  

The host is a VM running Ubuntu 22.04 LTS. All the previous steps of the Lab 3.2 went well. Searching online did not help.

Any thoughts?

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Comments

  • Posts: 2,443
    edited May 2022

    Hi @gustavo.lucenagomez,

    Did you happen to try the lab on the recommended guest OS Ubuntu 20.04 LTS? The current format of the lab guide has been tested on 20.04 LTS, and not yet on 22.04 LTS. I would expect things to change when the lab content will migrate to the latest LTS release.

    Regards,
    -Chris

  • Hey there @chrispokorni. Thank you for trying to help. Unfortunately no, I haven't tried it on 20.045 nor do I have the possiblity of doing so. In any case, if the distribution is the only source of the problem, it should be doable to find a solution I think ... :-)

  • (or do you think it is such a bad idea to try and proceed with this course on 22.04 ?)

  • Posts: 2,443

    Hi @gustavo.lucenagomez,

    I am currently investigating on Ubuntu 22 but I am not seeing consistent results. For me, the privileged container starts, but the unprivileged container does not. On Ubuntu 20 it is the exact opposite. So as of yet I do not have a workaround that would produce consistent results across environments.

    Regards,
    -Chris

  • I see, thanks.

    Should I expect more trouble down the road ? Would you advise I restart the course on a 20.04 Ubuntu? I mean I don't care about this particular exercise, it is the rest of the course that worries me

  • Posts: 2,443

    Hi @gustavo.lucenagomez,

    As of now, I only know of potential issues when installing Podman and Buildah in later chapters. All LXC, Podman, and Buildah related issues happened almost at once, at the same time as other Open Source projects have suffered minor complications. It all seems unrelated, but unexpected and frustrating nonetheless.

    While a temp workaround is posted here for Podman (on Ubuntu 20.04 LTS), I have yet to review the entire content of the lab guide to assess the overall impact and update steps where possibly needed.

    Regards,
    -Chris

  • Thanks.

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Categories

Upcoming Training