Cesar Talledo

Hi @mviereck, Thanks for giving Sysbox a shot and for adding support in x11docker for it, that would be AMAZING (you've done some great work with x11docker!). Regarding your question:...

I forgot to mention: we are currently working on removing the need for shiftfs in Sysbox, but this will require Linux kernel >= 5.12, as that introduces a feature called...

Hi @mviereck, That's great, thanks for the update. Responding to some of your questions: > Is there a way to disable userns in sysbox to avoid above limitations? No; we...

Hi @mviereck, Thanks for all that info, super useful. > Sysbox would do the ACL setup itself? A likely pitfall is to cleanly remove the ACLs once the container stops,...

Hi @mviereck, regarding: > At this point it might make sense to wait for integration of ID-mapped mounts in sysbox whether that fixes the issues with sockets, device files and...

Hi @johnstcn, thanks for filing the issue and for the excellent description. The issue has a fairly simple fix, but I am not sure that it's always the "right thing"...

> Processes running inside the container have no idea about how much CPU they have to work with. Out of curiosity, are you aware of any programs that look into...

Thanks @johnstcn for the detailed response. Not arguing against anything you said, but the thing that still confuses me a bit about applications that rely on the CFS quota/period is...

Another hint: I noticed that if I launch multiple sys containers with vagrant, and then destroy them, the destruction goes well for all but the last remaining sys container. In...

I also noticed another problem: when provisioning 16 sys containers with Vagrant (using the Docker provider with Sysbox), normally one of the containers fails to provision, with the following error:...