now that cgroup v2 is default (with Colima v0.6.0+), is there a CLI option to use cgroup v1 instead?

[rrevi]

Description

First, thanks to all Colima contributors.

I recently changed my workstation to an Apple silicon based MacBook Pro. Colima saved the date by easily, read great DX, allowing me to run container images based on the x86_64 architecture:

colima start --arch x86_64 --memory 12

🚀 🚀 🚀

While I got x86_64 containers running on my workstation, there is one container successfully starting but not successfully running (I know I know, weird thing to say, weird distinction). The container contains (no pun intended) the following errors:

Failed to read value from /sys/fs/cgroup/cpu/cpu.cfs_quota_us file. Skip the file and use auto setting for the configuration as default. Error: No such file or directory
Failed to read value from /sys/fs/cgroup/cpu/cpu.cfs_period_us file. Skip the file and use auto setting for the configuration as default. Error: No such file or directory

After some online search, I noticed with v0.6.0 of Colima, the cgroup version got upgraded to v2 by default. It seem to me that this one container is expecting to be running in a cgroup v1 env.

That is all a long way to say, is there a way (cli option?) to have Colima use cgroup v1? (as opposed to cgroup v2)

[sorobon]

This feature is very interesting :)

[rrevi]

In the meantime, downgrading to v0.5.6 as described in #877 does the trick 😄

[mvillafuertem]

Hi @rrevi, did you find any solution? I tried editing the config, but it didn't work for me either.

colima start -edit

docker:
  deprecatedCgroupv1: true

[rrevi]

Hi @rrevi, did you find any solution? I tried editing the config, but it didn't work for me either.

colima start -edit

docker:
  deprecatedCgroupv1: true

Hi @mvillafuertem , no, I am still running v0.5.6 as my solution 🤷