Fixed docker security

Running docker as sudo is not the best security.
https://engineering.bitnami.com/articles/why-non-root-containers-are-important-for-security.html

Instead of running container as root add user to docker group and there will no need for using sudo.
This commit is contained in:
kodxana 2020-09-28 20:22:58 +02:00 committed by GitHub
parent ae4e43b466
commit 91431922f5
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -25,6 +25,7 @@ sudo apt install -y docker-ce docker-ce-cli containerd.io && \
sudo systemctl enable docker && sudo systemctl start docker && \ sudo systemctl enable docker && sudo systemctl start docker && \
sudo curl -L "https://github.com/docker/compose/releases/download/1.24.1/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose && \ sudo curl -L "https://github.com/docker/compose/releases/download/1.24.1/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose && \
sudo chmod +x /usr/local/bin/docker-compose sudo chmod +x /usr/local/bin/docker-compose
sudo usermod -aG docker $USER
``` ```
@ -39,7 +40,7 @@ curl -L "https://raw.githubusercontent.com/lbryio/lbry-sdk/master/docker/docker-
### Start the servers ### Start the servers
``` ```
sudo docker-compose up --detach docker-compose up --detach
``` ```
### Check that everything worked ### Check that everything worked
@ -47,7 +48,7 @@ sudo docker-compose up --detach
The first time you start the wallet server, it will take a few minutes to download a recent snapshot of the database and extract it. You can follow the progress with The first time you start the wallet server, it will take a few minutes to download a recent snapshot of the database and extract it. You can follow the progress with
``` ```
sudo docker-compose logs --follow docker-compose logs --follow
``` ```
After the wallet server has caught up, it will bind to port 50001 and start responding to requests. You can check if this happened by running After the wallet server has caught up, it will bind to port 50001 and start responding to requests. You can check if this happened by running