Cesar Talledo

hi @isarkis, apologies for the delayed response but @rodnymolina has been out of office the last couple of weeks. I took a brief look at this issue a couple of...

Hi @isarkis, my apologies but I've been swamped with other Sysbox related work and have not had a chance to look into this yet. Will do my best to get...

Hi @rubenanapu , let us know if you would like to try the upcoming v0.5.0 version please. We are likely going to post a beta version of it on the...

Update: per [this AWS page]( https://aws.amazon.com/premiumsupport/knowledge-center/amazon-linux-2-kernel-upgrade/), AL2 now supports kernels up to 5.15, which should include ID-mapped-mounts, therefore allowing Sysbox to work on it (without shiftfs).

Hi @abhishady, Thanks for giving this a try (we've not had a chance to do it yet). > I tried to configures sysbox using daemonset manifest file in EKS cluster...

Hi @abhishady, Apologies for the late reply. I checked the code, and the error you are getting when installing Sysbox on your K8s cluster via the sysbox-deploy-k8s daemonset is due...

By the way, folks do run Sysbox on EKS, but they configure the EKS nodes to use Ubuntu (instead of AL2). Just thought I would mention it to see if...

Hi @supersat ... thanks for filing the issue. Let me take a closer look and will get back to you soon. I need to think carefully about what it would...

Hi @supersat, I've yet to look more closely at the security risks associated for relaxing the limits on the personality() syscall, but in the mean time, it's pretty easy to...

Hi @iamnoah, thanks for giving Sysbox a shot. I suspect the `fsgroup` section is causing the problem; could you try without it? That is, remove this: ``` securityContext: fsGroup: 999...