-
Notifications
You must be signed in to change notification settings - Fork 486
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
kamal 2: fixing docker user permission automatically on setup? #980
Comments
This is when you're using a non-root ssh user? Would be nice if that case didn't require anything special, yeah. Please do explore a PR. |
yes. going to draft a PR! |
The documentation notes that if we're using a non-root user, we need to manually bootstrap the server (https://kamal-deploy.org/docs/configuration/ssh/). I looked into codebase, and came up with this pseudo-code approach Lines 33 to 35 in e34031f
After line 34
|
@nikhilbhatt thanks! do you want to create this PR? |
@imWildCat Please go ahead as you have already opened up the issue and working on it. |
Probably better just to add another command sequence to
then add That's far easier to add to the existing |
This allows docker commands to function with a non-root ssh user Fixes: basecamp#980
This allows docker commands to function with a non-root ssh user Fixes: basecamp#980
I hope you'll forgive me for butting in here and opening the PR to fix this. Comments welcome. |
No worries at all! I’m too busy recent days. Apologies for the delay! |
This allows docker commands to function with a non-root ssh user Fixes: basecamp#980
This allows docker commands to function with a non-root ssh user Fixes: basecamp#980
This allows docker commands to function with a non-root ssh user Fixes: basecamp#980
This allows docker commands to function with a non-root ssh user Fixes: basecamp#980
+1 -- either having it automated as part of |
This allows docker commands to function with a non-root ssh user Fixes: basecamp#980
This allows docker commands to function with a non-root ssh user Fixes: basecamp#980
this issue has been existing from kamal 1
this is on a fresh setup
we have to run something like
if the team is ok with this I can open a PR
The text was updated successfully, but these errors were encountered: