Skip to content

Commit

Permalink
Remove duplicate instruction in ReadMe
Browse files Browse the repository at this point in the history
The docker-compose rebuilds the image, so it's a waste of time to build it first.
  • Loading branch information
TangentFoxy authored Oct 30, 2024
1 parent 54cc0e4 commit 082f616
Showing 1 changed file with 1 addition and 2 deletions.
3 changes: 1 addition & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,10 +44,9 @@ One could put Elk behind popular reverse proxies with SSL Handling like Traefik,

1. checkout source ```git clone https://github.com/elk-zone/elk.git```
1. got into new source dir: ```cd elk```
1. build Docker image: ```docker build .```
1. create local storage directory for settings: ```mkdir elk-storage```
1. adjust permissions of storage dir: ```sudo chown 911:911 ./elk-storage```
1. start container: ```docker-compose up -d```
1. build Docker image & start container: ```docker-compose up -d```

> [!NOTE]
> The provided Dockerfile creates a container which will eventually run Elk as non-root user and create a persistent named Docker volume upon first start (if that volume does not yet exist). This volume is always created with root permission. Failing to change the permissions of ```/elk/data``` inside this volume to UID:GID 911 (as specified for Elk in the Dockerfile) will prevent Elk from storing it's config for user accounts. You either have to fix the permission in the created named volume, or mount a directory with the correct permission to ```/elk/data``` into the container.
Expand Down

0 comments on commit 082f616

Please sign in to comment.