-
Notifications
You must be signed in to change notification settings - Fork 489
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
Update vulture container image to run as non-root #3764
base: main
Are you sure you want to change the base?
Conversation
@zalegrala would you mind having a look? |
cmd/tempo-vulture/Dockerfile
Outdated
RUN addgroup -g 10001 -S tempo && \ | ||
adduser -u 10001 -S tempo -G tempo | ||
|
||
RUN mkdir -p /var/tempo && \ |
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.
Vulture doesn't write data locally, and so the mkdir and associated chown aren't required.
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.
Thanks, fixed.
Follow-up to grafana#2265 which missed tempo-vulture Signed-off-by: Pedro Araujo <phcrva@gmail.com>
74069ce
to
a8ec52e
Compare
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.
This looks good to me. Did you have a chance to build an image and test it?
What this PR does:
Follow-up to #2265 which missed tempo-vulture
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]