chore(docker): run with zeebe user #11786
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
megglos
force-pushed
the
meg-11784-docker-user
branch
from
ae25660
to
daaee81
Compare
megglos
force-pushed
the
meg-11784-docker-user
branch
4 times, most recently
from
5de908b
to
6a06c82
Compare
megglos
force-pushed
the
meg-11784-docker-user
branch
from
6a06c82
to
7711681
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Runs the zeebe process with the zeebe user instead of root.
I couldn't make use of
USER zeeberight away as this would be breaking given a previous zeebe instance was running as root and thus file ownership being with root. I thus kept the initial user root but reapply file ownership to zeebe from the startup script and then switch to the zeebe user.As a follow-up we could introduce the
USER zeebestatement to the dockerfile and remove the added if block from the startup script. E.g. with zeebe 8.3.0.The changes to the Dockerfile could be backported to 8.1/8.0 and would allow users to configure the
zeebeuser manually in a new setup and not have trouble with mounting the log directory due to this. I would need to verify this on the stable branches though.Note:
Related issues
closes #11784