Cesar Talledo

FYI, we should have this soon (before end-of-year), as we are currently working on adding support for Sysbox in WSL2 for Docker Desktop.

> but if you bring your own container runtime, you're responsible for making sure that the kubelet's cgroup driver is the same as the container runtime. That's correct @brandond; it...

Hi @sibidharan, thanks for following up and apologies for the belated response. > Setting systemd.unified_cgroup_hierarchy=0 in grub fixes the issue. That's interesting and means the problem only occurs with cgroups...

Hi @concourse-sysbox, Thanks for giving Sysbox a shot for this use-case. Sysbox is made up of 3 components: [sysbox-runc, sysbox-fs, and sysbox-mgr](https://github.com/nestybox/sysbox/blob/master/docs/user-guide/design.md#sysbox-components). The latter two must be running before launching...

BTW, this error: > starting container process caused: process_linux.go:405: getting the final child's pid from pipe caused: EOF: unknown means that as soon as the sysbox-runc started the container process...

Hi @concourse-sysbox, > host ID mappings are non-contiguous: [{ContainerID:0 HostID:4294967294 Size:1} That error sounds like the `/etc/subuid` and `/etc/subgid` files may not be configured properly. How do these look? >...

> The contents of `/etc/sub{u|g}id` looks the same and as follows: > > ``` > ... > sysbox:493216:65536 > ``` OK that looks good: it's saying that user `sysbox` in...

> 'm symlinking my otherwise oci spec compatible runc binary to point over to sysbox-runc, and that's when I'm getting the error. Oh I see; that should work though. On...

> sudo sed -i --follow-symlinks '/^ExecStart/ s/$/ --allow-trusted-xattr=false/' /lib/systemd/system/sysbox-mgr.service Thanks @matthewparkinsondes; that means the bug is somewhere in the sysbox code that intercepts the xattr* syscalls inside the container. Fortunately...

> Thanks, the performance speed up when setting --allow-trusted-xattr=false in the following scenario is greater than two orders of magnitude (> 30 mins vs ~5 secs). That's a lot (!)...