-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Ensure docker in workspace works with fuse #8181
Conversation
Codecov Report
@@ Coverage Diff @@
## main #8181 +/- ##
==========================================
- Coverage 12.31% 11.17% -1.14%
==========================================
Files 20 18 -2
Lines 1161 993 -168
==========================================
- Hits 143 111 -32
+ Misses 1014 880 -134
+ Partials 4 2 -2
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Awesome👍 was there any man or documentation on the chroot phenomenon? Or is it a conclusion you understand from the phenomenon? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow - what a catch 🚀 Excellent work.
I also do not know why we chroot'ed instead of using pivot_root for fuse. Past us were silly enough not to add comments. I reckon it must have come from a misconception that pivot_root
did not/would not work for some reason. At this point, I cannot see adverse side-effects. Quite the contrary, I would expect pivot_root to work "better".
I already knew about the different behavior. The man pages for chroot and pivot_root explain the different behavior, but do not specifically contrast it with each other, so you need to have read both to notice the difference. |
I remember now! Thank you very much. |
Description
This fixes an issue where trying to run a docker container within a workspace would fail when fuse-overlayfs was used as shift method for the rootfs. Chroot only affects the calling process while pivot_root affects the whole mount namespace. @csweichel Do you know why chroot was used for fuse and pivot_root for shiftfs? Trying to understand if this would have other side effects.
Related Issue(s)
#8020
How to test
Side note: I am currently not able to get logs from ws-daemon or exec into it in my preview environment. I do not believe this has anything to do with my changes and should not affect anything but a second set of eyes on this would be good.
Release Notes
cc: @utam0k