-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue: Excessive Creation of Temporary Directories in Root with Sysbox #829
Comments
We have experiences this as well, and are currently working around it by manually cleaning up these empty directories. |
Hello @ctalledo @rodnymolina I have tested sysbox v0.6.5 on GKE 1.29 and still see When i execute Now my projects are broken, because i can't rollback to v0.6.4 since i need support of sysbox-fs emulation to allow writes to '/proc/sys/kernel/shm*' paths, and this feature was added in |
Fixes left-over .sysbox-procfs-* and .sysbox-sysfs-* dirs inside containers. They were being incorrectly left over by sysbox-fs nsenter processes. Fixes nestybox/sysbox#829. Signed-off-by: Cesar Talledo <cesar.talledo@docker.com>
Hi @EddieX64, apologies for the late reply. Thanks for letting me know, it was my mistake (thought I had fixed this in v0.6.5 but I made a mistake in the fix and did not catch it somehow). This PR will fix it once and for all: nestybox/sysbox-fs#100 We will generate a v0.6.6 release soon afterwards. |
Fixes left-over .sysbox-procfs-* and .sysbox-sysfs-* dirs inside containers. They were being incorrectly left over by sysbox-fs nsenter processes. Fixes nestybox/sysbox#829. Signed-off-by: Cesar Talledo <cesar.talledo@docker.com>
We are also experiencing the permissions problem with '/proc/sys/kernel/shm*' on certain builds. Is there a rough estimate when release 0.6.6 will be out? Or is there a Dev registry we can use in the meantime? Thanks. |
After all that, we seem to now be getting caught with this one - nestybox/sysbox-fs#101 Is that also in the next release @ctalledo ? |
Hi @aldcons,
We are targeting end of this week. It will fix both nestybox/sysbox-fs#100 and nestybox/sysbox-fs#101. Plus some other fixes.
There is no dev registry, but you can always build the sysbox package from source by cloning the sysbox repo.
This will generate the Sysbox Debian package under directory You can then install that on your host with If all is rignt, the |
Description:
We have observed that many temporary directories are being created in the root directory with names following the pattern
.sysbox-sysfs-<number>
. This is causing clutter and potential confusion.System Environment:
Additional Information:
This issue might have arisen because I masked the following services using systemctl:
$_ ls -hasl /
The text was updated successfully, but these errors were encountered: