-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
[Feat]: Improve Docker image usability by adding WORKDIR /etc/netdata #17890
Comments
Hey, @powerman. Please open one issue with all your suggestions. |
Sorry, I don't get it. These suggestions are not related, they should be handled independently, some may be accepted while other rejected… so what's the point in mixing them all in a single issue? Every other project insist on making separate issues/PRs for everything which can be separated… If you want to have one my issue max then just reopen any one from just closed ones, no matter which one. |
|
The question comes down to whether the entrypoint script and the agent itself actually correctly handle being run in |
Hmm. To me it's a different thing. |
Should we just |
Good idea! But it won't make WORKDIR change useless - when in a container if you're in |
FWIW Here is one-liner example to debug plugins in docker: sudo -u netdata -EH env -C /usr/libexec/netdata/plugins.d ./go.d.plugin -d -m nvidia_smi Maybe worth to add it somewhere in the docs too. |
Problem
Most of commands executed inside a docker container are
./edit-config
, which must be run in/etc/netdata
. So, each time afterdocker exec
we have to runcd /etc/netdata
, which is a bit annoying.Description
Make
/etc/netdata
default directory inside docker container.Importance
nice to have
Value proposition
cd
.Proposed implementation
Add
WORKDIR /etc/netdata
near the bottom of theDockerfile
.The text was updated successfully, but these errors were encountered: