Merge pull request #52 from Bockiii/ghcrupdate

Update ghcr references to lscr
pull/58/head
Adam 2022-05-21 11:37:02 +01:00 zatwierdzone przez GitHub
commit 0d9ef699e8
Nie znaleziono w bazie danych klucza dla tego podpisu
ID klucza GPG: 4AEE18F83AFDEB23
9 zmienionych plików z 61 dodań i 61 usunięć

Wyświetl plik

@ -74,7 +74,7 @@ docker create \
-p 80:80 `#optional` \ -p 80:80 `#optional` \
-v </path/to/appdata/config>:/config \ -v </path/to/appdata/config>:/config \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/swag lscr.io/linuxserver/swag
``` ```
## docker-compose ## docker-compose
@ -86,7 +86,7 @@ Compatible with docker-compose v2 schemas.
version: "2.1" version: "2.1"
services: services:
swag: swag:
image: ghcr.io/linuxserver/swag image: lscr.io/linuxserver/swag
container_name: swag container_name: swag
cap_add: cap_add:
- NET_ADMIN - NET_ADMIN
@ -184,7 +184,7 @@ docker create \
-p 80:80 \ -p 80:80 \
-v /home/aptalca/appdata/swag:/config \ -v /home/aptalca/appdata/swag:/config \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/swag lscr.io/linuxserver/swag
``` ```
Once created, we do `docker start swag` to start it. Once created, we do `docker start swag` to start it.
@ -196,7 +196,7 @@ With docker compose, we can use the following yml:
version: "2.1" version: "2.1"
services: services:
swag: swag:
image: ghcr.io/linuxserver/swag image: lscr.io/linuxserver/swag
container_name: swag container_name: swag
cap_add: cap_add:
- NET_ADMIN - NET_ADMIN
@ -249,7 +249,7 @@ docker create \
-p 80:80 \ -p 80:80 \
-v /home/aptalca/appdata/swag:/config \ -v /home/aptalca/appdata/swag:/config \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/swag lscr.io/linuxserver/swag
``` ```
And we start the container via `docker start swag` And we start the container via `docker start swag`
@ -261,7 +261,7 @@ With docker compose, we'll use:
version: "2.1" version: "2.1"
services: services:
swag: swag:
image: ghcr.io/linuxserver/swag image: lscr.io/linuxserver/swag
container_name: swag container_name: swag
cap_add: cap_add:
- NET_ADMIN - NET_ADMIN
@ -311,7 +311,7 @@ docker create \
-p 80:80 \ -p 80:80 \
-v /home/aptalca/appdata/swag:/config \ -v /home/aptalca/appdata/swag:/config \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/swag lscr.io/linuxserver/swag
``` ```
And we start the container via `docker start swag` And we start the container via `docker start swag`
@ -323,7 +323,7 @@ With docker compose, we'll use:
version: "2.1" version: "2.1"
services: services:
swag: swag:
image: ghcr.io/linuxserver/swag image: lscr.io/linuxserver/swag
container_name: swag container_name: swag
cap_add: cap_add:
- NET_ADMIN - NET_ADMIN
@ -388,7 +388,7 @@ Here's a docker compose stack to get both containers set up. For this exercise,
version: "2.1" version: "2.1"
services: services:
mariadb: mariadb:
image: ghcr.io/linuxserver/mariadb image: lscr.io/linuxserver/mariadb
container_name: mariadb container_name: mariadb
environment: environment:
- PUID=1000 - PUID=1000
@ -402,7 +402,7 @@ services:
- /home/aptalca/appdata/mariadb:/config - /home/aptalca/appdata/mariadb:/config
restart: unless-stopped restart: unless-stopped
swag: swag:
image: ghcr.io/linuxserver/swag image: lscr.io/linuxserver/swag
container_name: swag container_name: swag
cap_add: cap_add:
- NET_ADMIN - NET_ADMIN
@ -440,7 +440,7 @@ docker create \
-e MYSQL_PASSWORD=WP_dbpassword \ -e MYSQL_PASSWORD=WP_dbpassword \
-v /home/aptalca/appdata/mariadb:/config \ -v /home/aptalca/appdata/mariadb:/config \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/mariadb lscr.io/linuxserver/mariadb
``` ```
SWAG: SWAG:
@ -461,7 +461,7 @@ docker create \
-p 80:80 \ -p 80:80 \
-v /home/aptalca/appdata/swag:/config \ -v /home/aptalca/appdata/swag:/config \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/swag lscr.io/linuxserver/swag
``` ```
Once the SWAG container is set up with ssl certs and the webserver is up, we'll download the latest Wordpress and untar it into our www folder: Once the SWAG container is set up with ssl certs and the webserver is up, we'll download the latest Wordpress and untar it into our www folder:
@ -741,7 +741,7 @@ Here's a docker compose stack we can use to set up both containers:
version: "2.1" version: "2.1"
services: services:
ombi: ombi:
image: ghcr.io/linuxserver/ombi image: lscr.io/linuxserver/ombi
container_name: ombi container_name: ombi
environment: environment:
- PUID=1000 - PUID=1000
@ -753,7 +753,7 @@ services:
- 3579:3579 - 3579:3579
restart: unless-stopped restart: unless-stopped
swag: swag:
image: ghcr.io/linuxserver/swag image: lscr.io/linuxserver/swag
container_name: swag container_name: swag
cap_add: cap_add:
- NET_ADMIN - NET_ADMIN
@ -786,7 +786,7 @@ docker create \
-p 3579:3579 \ -p 3579:3579 \
-v /home/aptalca/appdata/ombi:/config \ -v /home/aptalca/appdata/ombi:/config \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/ombi lscr.io/linuxserver/ombi
``` ```
SWAG: SWAG:
@ -807,7 +807,7 @@ docker create \
-p 80:80 \ -p 80:80 \
-v /home/aptalca/appdata/swag:/config \ -v /home/aptalca/appdata/swag:/config \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/swag lscr.io/linuxserver/swag
``` ```
Once our containers up and running (and we confirm we can reach the placeholder page at `https://linuxserver-test.com`), we simply rename the file `ombi.subdomain.conf.sample` under `/config/nginx/proxy-confs/` to `ombi.subdomain.conf` and we restart the SWAG container. Now when we browser to `https://ombi.linuxserver-test.com` we should see the Ombi gui. Once our containers up and running (and we confirm we can reach the placeholder page at `https://linuxserver-test.com`), we simply rename the file `ombi.subdomain.conf.sample` under `/config/nginx/proxy-confs/` to `ombi.subdomain.conf` and we restart the SWAG container. Now when we browser to `https://ombi.linuxserver-test.com` we should see the Ombi gui.
@ -828,7 +828,7 @@ Here's a docker compose stack to set up our SWAG, nextcloud and mariadb containe
version: "2.1" version: "2.1"
services: services:
nextcloud: nextcloud:
image: ghcr.io/linuxserver/nextcloud image: lscr.io/linuxserver/nextcloud
container_name: nextcloud container_name: nextcloud
environment: environment:
- PUID=1000 - PUID=1000
@ -841,7 +841,7 @@ services:
- mariadb - mariadb
restart: unless-stopped restart: unless-stopped
mariadb: mariadb:
image: ghcr.io/linuxserver/mariadb image: lscr.io/linuxserver/mariadb
container_name: mariadb container_name: mariadb
environment: environment:
- PUID=1000 - PUID=1000
@ -855,7 +855,7 @@ services:
- /home/aptalca/appdata/mariadb:/config - /home/aptalca/appdata/mariadb:/config
restart: unless-stopped restart: unless-stopped
swag: swag:
image: ghcr.io/linuxserver/swag image: lscr.io/linuxserver/swag
container_name: swag container_name: swag
cap_add: cap_add:
- NET_ADMIN - NET_ADMIN
@ -888,7 +888,7 @@ docker create \
-v /home/aptalca/appdata/nextcloud/config:/config \ -v /home/aptalca/appdata/nextcloud/config:/config \
-v /home/aptalca/appdata/nextcloud/data:/data \ -v /home/aptalca/appdata/nextcloud/data:/data \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/nextcloud lscr.io/linuxserver/nextcloud
``` ```
Mariadb: Mariadb:
@ -906,7 +906,7 @@ docker create \
-e MYSQL_PASSWORD=ncpassword \ -e MYSQL_PASSWORD=ncpassword \
-v /home/aptalca/appdata/mariadb:/config \ -v /home/aptalca/appdata/mariadb:/config \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/mariadb lscr.io/linuxserver/mariadb
``` ```
SWAG: SWAG:
@ -927,7 +927,7 @@ docker create \
-p 80:80 \ -p 80:80 \
-v /home/aptalca/appdata/swag:/config \ -v /home/aptalca/appdata/swag:/config \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/swag lscr.io/linuxserver/swag
``` ```
Now we find the file named `nextcloud.subdomain.conf.sample` under SWAG's `/config/nginx/proxy-confs` folder and rename it to `nextcloud.subdomain.conf`, then restart the SWAG container. Now we find the file named `nextcloud.subdomain.conf.sample` under SWAG's `/config/nginx/proxy-confs` folder and rename it to `nextcloud.subdomain.conf`, then restart the SWAG container.
@ -975,7 +975,7 @@ Here's a docker compose stack we can use to set up both containers:
version: "2.1" version: "2.1"
services: services:
plex: plex:
image: ghcr.io/linuxserver/plex image: lscr.io/linuxserver/plex
container_name: plex container_name: plex
network_mode: host network_mode: host
environment: environment:
@ -988,7 +988,7 @@ services:
- /home/aptalca/movies:/data/movies - /home/aptalca/movies:/data/movies
restart: unless-stopped restart: unless-stopped
swag: swag:
image: ghcr.io/linuxserver/swag image: lscr.io/linuxserver/swag
container_name: swag container_name: swag
cap_add: cap_add:
- NET_ADMIN - NET_ADMIN
@ -1022,7 +1022,7 @@ docker create \
-v /home/aptalca/tvshows:/data/tvshows \ -v /home/aptalca/tvshows:/data/tvshows \
-v /home/aptalca/movies:/data/movies \ -v /home/aptalca/movies:/data/movies \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/plex lscr.io/linuxserver/plex
``` ```
SWAG: SWAG:
@ -1043,7 +1043,7 @@ docker create \
-p 80:80 \ -p 80:80 \
-v /home/aptalca/appdata/swag:/config \ -v /home/aptalca/appdata/swag:/config \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/swag lscr.io/linuxserver/swag
``` ```
Once the containers are set up, we browse to `http://LOCALSERVERIP:32400/web` and set up our Plex server with our Plex account. Then we can find the file named `plex.subfolder.conf.sample` under our SWAG container's `/config/nginx/proxy-confs` folder and rename it to `plex.subfolder.conf`. Once the containers are set up, we browse to `http://LOCALSERVERIP:32400/web` and set up our Plex server with our Plex account. Then we can find the file named `plex.subfolder.conf.sample` under our SWAG container's `/config/nginx/proxy-confs` folder and rename it to `plex.subfolder.conf`.
@ -1067,7 +1067,7 @@ Here's a docker compose stack we can use to set up both containers:
version: "2.1" version: "2.1"
services: services:
heimdall: heimdall:
image: ghcr.io/linuxserver/heimdall image: lscr.io/linuxserver/heimdall
container_name: heimdall container_name: heimdall
environment: environment:
- PUID=1000 - PUID=1000
@ -1077,7 +1077,7 @@ services:
- /home/aptalca/appdata/heimdall:/config - /home/aptalca/appdata/heimdall:/config
restart: unless-stopped restart: unless-stopped
swag: swag:
image: ghcr.io/linuxserver/swag image: lscr.io/linuxserver/swag
container_name: swag container_name: swag
cap_add: cap_add:
- NET_ADMIN - NET_ADMIN
@ -1109,7 +1109,7 @@ docker create \
-e TZ=Europe/London \ -e TZ=Europe/London \
-v /home/aptalca/appdata/heimdall:/config \ -v /home/aptalca/appdata/heimdall:/config \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/heimdall lscr.io/linuxserver/heimdall
``` ```
SWAG: SWAG:
@ -1130,7 +1130,7 @@ docker create \
-p 80:80 \ -p 80:80 \
-v /home/aptalca/appdata/swag:/config \ -v /home/aptalca/appdata/swag:/config \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/swag lscr.io/linuxserver/swag
``` ```
Once the containers are set up, we'll find the file named `heimdall.subfolder.conf.sample` under SWAG's `/config/nginx/proxy-confs` folder and rename it to `heimdall.subfolder.conf`. If we look inside that conf file, we'll see that it is set to use `location / {`, which will cause an issue because there is already a location defined for `/` inside the default site config for SWAG. So we need to edit the default site config at `/config/nginx/site-confs/default` and comment out the location block for `/` inside our main server block so it reads: Once the containers are set up, we'll find the file named `heimdall.subfolder.conf.sample` under SWAG's `/config/nginx/proxy-confs` folder and rename it to `heimdall.subfolder.conf`. If we look inside that conf file, we'll see that it is set to use `location / {`, which will cause an issue because there is already a location defined for `/` inside the default site config for SWAG. So we need to edit the default site config at `/config/nginx/site-confs/default` and comment out the location block for `/` inside our main server block so it reads:

Wyświetl plik

@ -19,7 +19,7 @@ CodiMD is a real-time, multi-platform collaborative markdown note editor. This
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/). 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 `ghcr.io/linuxserver/codimd` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. Simply pulling `lscr.io/linuxserver/codimd` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are: The architectures supported by this image are:
@ -93,7 +93,7 @@ docker run -d \
-p 3000:3000 \ -p 3000:3000 \
-v </path/to/appdata>:/config \ -v </path/to/appdata>:/config \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/codimd lscr.io/linuxserver/codimd
``` ```
@ -188,7 +188,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number * Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' codimd` * `docker inspect -f '{{ index .Config.Labels "build_version" }}' codimd`
* Image version number * Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' ghcr.io/linuxserver/codimd` * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/codimd`
## Versions ## Versions

Wyświetl plik

@ -16,7 +16,7 @@
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/). 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 `ghcr.io/linuxserver/hydra` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. Simply pulling `lscr.io/linuxserver/hydra` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are: The architectures supported by this image are:
@ -40,7 +40,7 @@ Compatible with docker-compose v2 schemas.
version: "2.1" version: "2.1"
services: services:
hydra: hydra:
image: ghcr.io/linuxserver/hydra image: lscr.io/linuxserver/hydra
container_name: hydra container_name: hydra
environment: environment:
- PUID=1000 - PUID=1000
@ -66,7 +66,7 @@ docker run -d \
-v <path to data>:/config \ -v <path to data>:/config \
-v <nzb download>:/downloads \ -v <nzb download>:/downloads \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/hydra lscr.io/linuxserver/hydra
``` ```
@ -153,7 +153,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number * Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' hydra` * `docker inspect -f '{{ index .Config.Labels "build_version" }}' hydra`
* Image version number * Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' ghcr.io/linuxserver/hydra` * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/hydra`
## Versions ## Versions

Wyświetl plik

@ -54,7 +54,7 @@ To help you get started creating a container from this image you can either use
version: "3" version: "3"
services: services:
mariadb: mariadb:
image: ghcr.io/linuxserver/mariadb:latest image: lscr.io/linuxserver/mariadb:latest
container_name: lychee_mariadb container_name: lychee_mariadb
restart: always restart: always
volumes: volumes:
@ -68,7 +68,7 @@ services:
- PUID=1000 - PUID=1000
- TZ=Europe/London - TZ=Europe/London
lychee: lychee:
image: ghcr.io/linuxserver/lychee:latest image: lscr.io/linuxserver/lychee:latest
container_name: lychee container_name: lychee
restart: always restart: always
depends_on: depends_on:

Wyświetl plik

@ -46,7 +46,7 @@ Find us at:
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/). 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 `ghcr.io/linuxserver/musicbrainz` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. Simply pulling `lscr.io/linuxserver/musicbrainz` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are: The architectures supported by this image are:
@ -70,7 +70,7 @@ Compatible with docker-compose v2 schemas.
version: "2.1" version: "2.1"
services: services:
musicbrainz: musicbrainz:
image: ghcr.io/linuxserver/musicbrainz image: lscr.io/linuxserver/musicbrainz
container_name: musicbrainz container_name: musicbrainz
environment: environment:
- PUID=1000 - PUID=1000
@ -102,7 +102,7 @@ docker run -d \
-v </path/to/appdata/config>:/config \ -v </path/to/appdata/config>:/config \
-v </path/to/appdata/config>:/data \ -v </path/to/appdata/config>:/data \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/musicbrainz lscr.io/linuxserver/musicbrainz
``` ```
@ -178,7 +178,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* container version number * container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' musicbrainz` * `docker inspect -f '{{ index .Config.Labels "build_version" }}' musicbrainz`
* image version number * image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' ghcr.io/linuxserver/musicbrainz` * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/musicbrainz`
## Updating Info ## Updating Info
@ -194,7 +194,7 @@ Below are the instructions for updating containers:
* You can also remove the old dangling images: `docker image prune` * You can also remove the old dangling images: `docker image prune`
### Via Docker Run ### Via Docker Run
* Update the image: `docker pull ghcr.io/linuxserver/musicbrainz` * Update the image: `docker pull lscr.io/linuxserver/musicbrainz`
* Stop the running container: `docker stop musicbrainz` * Stop the running container: `docker stop musicbrainz`
* Delete the container: `docker rm musicbrainz` * Delete the container: `docker rm musicbrainz`
* Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your `/config` folder and settings will be preserved) * Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your `/config` folder and settings will be preserved)
@ -224,7 +224,7 @@ cd docker-musicbrainz
docker build \ docker build \
--no-cache \ --no-cache \
--pull \ --pull \
-t ghcr.io/linuxserver/musicbrainz:latest . -t lscr.io/linuxserver/musicbrainz:latest .
``` ```
The ARM variants can be built on x86_64 hardware using `multiarch/qemu-user-static` The ARM variants can be built on x86_64 hardware using `multiarch/qemu-user-static`

Wyświetl plik

@ -16,7 +16,7 @@
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/). 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 `ghcr.io/linuxserver/mylar` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. Simply pulling `lscr.io/linuxserver/mylar` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are: The architectures supported by this image are:
@ -40,7 +40,7 @@ Compatible with docker-compose v2 schemas.
version: "2.1" version: "2.1"
services: services:
mylar: mylar:
image: ghcr.io/linuxserver/mylar image: lscr.io/linuxserver/mylar
container_name: mylar container_name: mylar
environment: environment:
- PUID=1000 - PUID=1000
@ -66,7 +66,7 @@ docker run -d \
-v <comics-folder>:/comics \ -v <comics-folder>:/comics \
-v <downloads-folder>:/downloads \ -v <downloads-folder>:/downloads \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/mylar lscr.io/linuxserver/mylar
``` ```
@ -152,7 +152,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number * Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' mylar` * `docker inspect -f '{{ index .Config.Labels "build_version" }}' mylar`
* Image version number * Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' ghcr.io/linuxserver/mylar` * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/mylar`
## Versions ## Versions

Wyświetl plik

@ -28,7 +28,7 @@ https://github.com/linuxserver/docker-wireguard
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/). 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 `ghcr.io/linuxserver/openvpn-as` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. Simply pulling `lscr.io/linuxserver/openvpn-as` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are: The architectures supported by this image are:
@ -73,7 +73,7 @@ Compatible with docker-compose v2 schemas.
version: "2.1" version: "2.1"
services: services:
openvpn-as: openvpn-as:
image: ghcr.io/linuxserver/openvpn-as image: lscr.io/linuxserver/openvpn-as
container_name: openvpn-as container_name: openvpn-as
cap_add: cap_add:
- NET_ADMIN - NET_ADMIN
@ -106,7 +106,7 @@ docker run -d \
-p 1194:1194/udp \ -p 1194:1194/udp \
-v <path to data>:/config \ -v <path to data>:/config \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/openvpn-as lscr.io/linuxserver/openvpn-as
``` ```
## Parameters ## Parameters
@ -181,7 +181,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number * Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' openvpn-as` * `docker inspect -f '{{ index .Config.Labels "build_version" }}' openvpn-as`
* Image version number * Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' ghcr.io/linuxserver/openvpn-as` * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/openvpn-as`
## Versions ## Versions

Wyświetl plik

@ -19,7 +19,7 @@ title: pydio
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/). 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 `ghcr.io/linuxserver/pydio` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. Simply pulling `lscr.io/linuxserver/pydio` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are: The architectures supported by this image are:
@ -43,7 +43,7 @@ Compatible with docker-compose v2 schemas.
version: "2.1" version: "2.1"
services: services:
pydio: pydio:
image: ghcr.io/linuxserver/pydio image: lscr.io/linuxserver/pydio
container_name: pydio container_name: pydio
environment: environment:
- PUID=1000 - PUID=1000
@ -69,7 +69,7 @@ docker run -d \
-v <path to data>:/config \ -v <path to data>:/config \
-v <path to data>:/data \ -v <path to data>:/data \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/pydio lscr.io/linuxserver/pydio
``` ```
@ -161,7 +161,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number * Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' pydio` * `docker inspect -f '{{ index .Config.Labels "build_version" }}' pydio`
* Image version number * Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' ghcr.io/linuxserver/pydio` * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/pydio`
## Versions ## Versions

Wyświetl plik

@ -19,7 +19,7 @@ title: rutorrent
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/). 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 `ghcr.io/linuxserver/rutorrent` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. Simply pulling `lscr.io/linuxserver/rutorrent` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are: The architectures supported by this image are:
@ -43,7 +43,7 @@ Compatible with docker-compose v2 schemas.
version: "2.1" version: "2.1"
services: services:
rutorrent: rutorrent:
image: ghcr.io/linuxserver/rutorrent image: lscr.io/linuxserver/rutorrent
container_name: rutorrent container_name: rutorrent
environment: environment:
- PUID=1000 - PUID=1000
@ -73,7 +73,7 @@ docker run -d \
-v </path/to/rutorrent/config>:/config \ -v </path/to/rutorrent/config>:/config \
-v </path/to/rutorrent/downloads>:/downloads \ -v </path/to/rutorrent/downloads>:/downloads \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/linuxserver/rutorrent lscr.io/linuxserver/rutorrent
``` ```
@ -188,7 +188,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number * Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' rutorrent` * `docker inspect -f '{{ index .Config.Labels "build_version" }}' rutorrent`
* Image version number * Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' ghcr.io/linuxserver/rutorrent` * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/rutorrent`
## Versions ## Versions