diff --git a/images/docker-heimdall.md b/images/docker-heimdall.md index f5403b0cc7..40b01aa751 100755 --- a/images/docker-heimdall.md +++ b/images/docker-heimdall.md @@ -14,7 +14,7 @@ Why not use it as your browser start page? It even has the ability to include a ## Supported Architectures -Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list). +Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/). Simply pulling `linuxserver/heimdall` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. @@ -36,8 +36,8 @@ Here are some example snippets to help you get started creating a container from ``` docker create \ --name=heimdall \ - -e PUID=1001 \ - -e PGID=1001 \ + -e PUID=1000 \ + -e PGID=1000 \ -e TZ=Europe/London \ -p 80:80 \ -p 443:443 \ @@ -46,10 +46,10 @@ docker create \ linuxserver/heimdall ``` -Using tags, you can switch between the stable releases of Heimdall and the master branch. No tag is required for the latest stable release. -Add the development tag, if required, to the linuxserver/heimdall line of the run/create command in the following format, linuxserver/heimdall:development -The development tag will be the latest commit in the master branch of Heimdall. -HOWEVER , USE THE DEVELOPMENT TAG AT YOUR OWN PERIL !!!!!!!!! +Using tags, you can switch between the stable releases of Heimdall and the master branch. No tag is required for the latest stable release. +Add the `development` tag, if required, to the `linuxserver/heimdall` line of the run/create command in the following format, `linuxserver/heimdall:development`. +The `development` tag will be the latest commit in the master branch of Heimdall. +HOWEVER, USE THE DEVELOPMENT TAG AT YOUR OWN PERIL !!!!!!!!! ### docker-compose @@ -64,15 +64,14 @@ services: image: linuxserver/heimdall container_name: heimdall environment: - - PUID=1001 - - PGID=1001 + - PUID=1000 + - PGID=1000 - TZ=Europe/London volumes: - :/config ports: - 80:80 - 443:443 - mem_limit: 4096m restart: unless-stopped ``` @@ -92,8 +91,8 @@ Docker images are configured using parameters passed at runtime (such as those a | Env | Function | | :----: | --- | -| `PUID=1001` | for UserID - see below for explanation | -| `PGID=1001` | for GroupID - see below for explanation | +| `PUID=1000` | for UserID - see below for explanation | +| `PGID=1000` | for GroupID - see below for explanation | | `TZ=Europe/London` | Specify a timezone to use EG Europe/London | ### Volume Mappings (`-v`) @@ -110,11 +109,11 @@ When using volumes (`-v` flags), permissions issues can arise between the host O Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic. -In this instance `PUID=1001` and `PGID=1001`, to find yours use `id user` as below: +In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below: ``` $ id username - uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup) + uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup) ``` ## Application Setup @@ -142,6 +141,8 @@ This image now supports password protection through htpasswd. Run the following ## Versions * **22.02.19:** - Rebasing to alpine 3.9. +* **16.01.18:** - Generate random app key in .env for new installs. +* **20.11.18:** - Upgrade baseimage packages during build. * **04.11.18:** - Add php7-zip. * **31.10.18:** - Add queue service. * **17.10.18:** - Symlink avatars folder.