-
Notifications
You must be signed in to change notification settings - Fork 784
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
[Merged by Bors] - Creates a new lighthouse user and makes it the default user to be use… #1502
Conversation
…d in the Docker image
Do the startup scripts in lighthouse-docker need to change to reflect the new lighthouse user? |
@acequicksilver they should not need any changes as far as I can see. I ran |
start-beacon-node.sh references the root home directory --network-dir /root/network and there will be some references in the docker compose-compose.yml |
@acequicksilver Good catch. Could simply change it to the environment variabale For the |
@acequicksilver I cant find the reference you mention. Updated the relevant part in the book though. If this PR lands I will be happy to update |
I should have included a link. See below https://github.com/sigp/lighthouse-docker/blob/master/docker-compose.yml https://github.com/sigp/lighthouse-docker/blob/master/scripts/start-beacon-node.sh Thanks |
@acequicksilver Okay, but this is unrelated to this repository. That shoudnt be touched before this change is actually included here I believe. |
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 seems good to me.
Better practice to use non-root users in docker imo.
I'll update the docker-compose scripts once this gets merged in also and the image gets uploaded (if you don't see this time and want to do it yourself) Thanks guys! |
bors r+ |
Build failed: |
@AgeManning is the CI test failure related to changes in here?
|
@b-m-f Nah, unfortunately the macOS VMs are a bit flaky and occasionally seem to timeout bors retry |
Pull request successfully merged into master. Build succeeded: |
## Issue Addressed The lighthouse user has recently changed to `lighthouse` from root. This requires uses to change ownership of their current docker mounted volumes and the upgrade path is non-trivial. This reverts #1502 and we will include it in a major release in the future. ## Proposed Changes N/A ## Additional Info N/A
## Issue Addressed The lighthouse user has recently changed to `lighthouse` from root. This requires uses to change ownership of their current docker mounted volumes and the upgrade path is non-trivial. This reverts sigp#1502 and we will include it in a major release in the future. ## Proposed Changes N/A ## Additional Info N/A
…d in the Docker image
Issue Addressed
#1459
Proposed Changes
lighthouse
user and group in Docker container