-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
rootless: write the custom config file before reload #2670
rootless: write the custom config file before reload #2670
Conversation
so that when we do a rootlessReload we inherit the correct settings from the command line. Signed-off-by: Giuseppe Scrivano <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: giuseppe The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@tobwen please update this PR if it solves the issues you were having or if we need to do more changes |
@giuseppe Sorry, no change...
|
That's coming out of runc, looks like. Can you add a --log-level=debug and pastebin anything that pops up in syslog from Conmon ( |
@giuseppe funny thing:
Seems like we're limited to less than 6 chars? |
or we will easily pass the 108 chars limits for unix paths. Signed-off-by: Giuseppe Scrivano <[email protected]>
@giuseppe Works for me! Thanks. |
LGTM, all green test buttons. |
marked as WIP for the comments here: #2659 |
split the generation for the default storage.conf and when we write it if not existing for a rootless user. This is necessary because during the startup we might be overriding the default configuration through --storage-driver and --storage-opt, that would not be written down to the storage.conf file we generated. Closes: containers#2659 Signed-off-by: Giuseppe Scrivano <[email protected]>
dropped WIP, the patch seems to solve the issue cc @tobwen |
@giuseppe Thanks. From my side LGTM, but I'm a user only :) |
since you reported the initial issue, your feedback is very important :-) |
/lgtm |
storageOpts.RunRoot = defaultRootlessRunRoot | ||
} | ||
if storageOpts.GraphRoot == "" { | ||
storageOpts.GraphRoot = defaultRootlessGraphRoot |
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.
@giuseppe Probably a matter for a separate PR, but would it be worth also setting overlay and overlay mountprogram in the defaults here? Might fix a lot of our "overlayfs is not supported over this filesystem" errors
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.
I can do that, should I hardcode it to "/usr/bin/fuse-overlayfs"?
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.
I think that ought to be fine - even if it doesn't exist, we get a much nicer error than the current "overlay is not supported over this filesystem" one
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.
hm.. looking at the code that should not really happen, if fuse-overlayfs is not found then it uses vfs
It might happen id the user forces the storage to be type “overlay”. |
unprivileged overlay is enabled on some kernels, we still want to give the user an option for enabling it, so we cannot set fuse-overlayfs blindly. What we can possibly do is improving the error message |
so that when we do a rootlessReload we inherit the correct settings
from the command line.
Signed-off-by: Giuseppe Scrivano [email protected]