Cesar Talledo

Thanks @lsoica. > With k3s there's no kubelet binary. That's correct, and it makes it very difficult for sysbox-deploy-k8s to work with K3s since it needs to reconfigure the kubelet...

Thanks @mhornbacher for your contribution to resolving this issue, much appreciated!

Hi @DekusDenial, > will the [upcoming 0.6.3] release cover the fix for https://github.com/nestybox/sysbox/issues/592#issuecomment-1611783474? I am not sure; I see a few related commits, but nothing that specifically addresses that issue....

> I enabled qemu on a host and run sysbox container but /proc/sys/fs/binfmt_misc was empty and didnt inherit from the host I see; no unfortunately the ability to expose (i.e.,...

> That’s the reason we still pin to 0.6.1 given the situation in which we have no other mean to enable qemu for multi-arch workload. Got it; would the work-around...

> Unfortunately no because our setup and use case is not the same as above, and based on the reporter’s comment above this issue also prevented them from moving to...

> Meanwhile, if you can provide the sources where this config would be implemented or another word where this binfmt_misc resource would be excluded from isolation, people can patch it...

Hi folks, closing this ticket as Sysbox v0.6.2 no longer requires shiftfs on kernels >= 5.12; see [here](https://github.com/nestybox/sysbox/blob/master/docs/user-guide/design.md#shiftfs-module) for more info. Also, Sysbox v0.6.2 checks if shiftfs is present and...

Hi @errordeveloper, thanks for the tip. > you need to run scripts/update-component-sha.sh and check the results in also Got it; I've done that now (i.e., obtained the new tag with:...

Hi @errordeveloper, gentle nudge to see if I can get approval for this PR. Thanks!