-
-
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
ERROR: ~/.config: read-only file system #569
Comments
Hi @jesseduffield , You will provide a solution for this? |
I have no intentions on fixing this anytime soon, but I will happily review a PR. Would you be up to the task? |
Hey, I'd be happy to contribute. But after some search I've found this env variable CONFIG_DIR. CONFIG_DIR=/some_other_place lazydocker |
I'm running for local user with sudo for current environment and it works. but there is cli argument that I don't know what does it mean/, existing for. the --config print default configuration. but description says "current default". which have no sense |
+ fix select in (fallback from fzf) + disable mouse + fix no logs. see: jesseduffield/lazydocker#569 jesseduffield/lazydocker#218 jesseduffield/lazydocker#574
Describe the bug
Inside some frugal Linux distributions the root directory is read-only. When running it as root you receive this error:
mkdir /root/.config: read-only file system
Additional context
You need to provide one command line parameter to configure an alternative config directory. Or in case of failing use another path (i.e.
/run/lazydocker
)The text was updated successfully, but these errors were encountered: