fix(docker): allow the zebra
user access to relevant dirs
#8817
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.
Motivation
When running a Zebra node using Docker without a privileged user, you won't be able to modify some files and directories, not even the ones in the current directory, as the
zebra
user has no permission to/
.Solution
The best way to solve this is making the
/opt/zebrad
the currentWORKDIR
. This also requires moving theentrypoint.sh
from the root/
directory to/etc/zebrad
as this directory is used to save configuration, and other files.An
APP_HOME
ARG is used as not all platforms where a Docker container is deployed allows writting permissions to the/opt
directory. This allow some users to re-build the image with a customWORKDIR
PR Author's Checklist
PR Reviewer's Checklist