You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have two default vagrant files, one vagrantfile for podman and one vagrantfile for containerd. Out of these the default ones are broken see #2882 . We also run into issues as mentioned in #361 (comment) where contributors don't have access to specific cgroup envs, and have problems.
We should have some vagrant files that can be used as the "standard" developing environment making it easier for devs and testing.
Currently I'm thinking of following files :
One file with cgroups v1 setup
One file with cgroups v2 setup, and as podman and containerd both need v2, we can also have their deps in here.
I think this would make the development and testing easier .
The text was updated successfully, but these errors were encountered:
After the comment, I have done some study about using VMs as dev environment. I wonder if testing youki with LXD system container would be lighter and more friendly. According to the official guide, docker and containerd seems working fine in the system container.
Currently we have two default vagrant files, one vagrantfile for podman and one vagrantfile for containerd. Out of these the default ones are broken see #2882 . We also run into issues as mentioned in #361 (comment) where contributors don't have access to specific cgroup envs, and have problems.
We should have some vagrant files that can be used as the "standard" developing environment making it easier for devs and testing.
Currently I'm thinking of following files :
I think this would make the development and testing easier .
The text was updated successfully, but these errors were encountered: