Cesar Talledo

Thanks @gaetanmetzger. Unfortunately we have no cycles at this time, but happy to accept a contribution. It shouldn't be too difficult to do, just takes a bit of time.

Hi @chris-gputrader, thanks for reporting. What distro and kernel are you on? `lsb_release -a` `uname -a` Also, can you provide the output of the sysbox-mgr (`journalctl -u sysbox-mgr`), particularly the...

Hi @cavedon, thanks for trying Sysbox and reporting the issue. Your observation is correct: when a Sysbox container stops, Sysbox transfers data from `/var/lib/sysbox/docker/` to the container's nominal rootfs on...

Hi @MrPeacockNLB , thanks for reporting the issue. @rodnymolina: I suspect the problem is caused by this commit: ``` commit 76c732f519ad8ae58dcf8f6fad6646bb4fa9d7ec Author: Rodny Molina Date: Fri Jul 5 11:00:56 2024...

Hi @cloudzhongtian, thanks for filing the issue. Can you please add steps for us to reproduce? Thanks!

Thanks @vanackere for reporting, I'll take a look ASAP.

I was able to reproduce easily on a Ubuntu-25.04 host; I'll investigate what's going on.

@vanackere, @abhi4u1947, no update yet but I am looking at it right now.

OK, got to the bottom of this: In Ubuntu 25.04 (Plucky), an [apparmor](https://apparmor.net/) profile for the `fusermount3` utility has been added under `/etc/apparmor.d/fusermount3`, and it's blocking Sysbox from creating filesystem-in-userspace...

> In the meantime, edit the `/etc/apparmor.d/fusermount3` file and add the following entries to it: Alternatively, you can edit the "local" version of this file under `/etc/apparmor.d/local/fusermount3` and simply add...