For some reason my Nextcloud stack when deployed tries to basically pull all available images from ghcr.io/linuxserver/nextcloud until it fails due to running out of disk space. Here are some of the images it pulled as an example (I'm not on an ARM cpu):
Code
sha256:f346c7a6d867c5a0efb16b30f79174... Unused ghcr.io/linuxserver/nextcloud:arm64v8-21.0.0-ls124 384.5 MB 2021-02-25 22:01:40
sha256:cfdcfabf18da6564986ed8aa2b44f5... Unused ghcr.io/linuxserver/nextcloud:arm32v7-21.0.0-ls124 334.7 MB 2021-02-25 21:58:44
sha256:fb6a9727905a29d2985fbe798ed15e... Unused ghcr.io/linuxserver/nextcloud:21.0.0-ls124ghcr.io/linuxserver/nextcloud:amd64-21.0.0-ls124 395.4 MB 2021-02-25 21:58:14
sha256:833fc473deb034860bdb04895e3016... Unused ghcr.io/linuxserver/nextcloud:arm64v8-21.0.0-ls123 387.7 MB 2021-02-22 15:34:56
sha256:5266b2eb3602603d10aa2ec54f8d9a... Unused ghcr.io/linuxserver/nextcloud:arm32v7-21.0.0-ls123 336.9 MB 2021-02-22 15:24:13
I've deployed the stack in Portainer using the instructions found here [How-To] Nextcloud with Letsencrypt using OMV and docker-compose .
And here is my docker-compose.yml:
Code
version: "2"
services:
nextcloud:
image: ghcr.io/linuxserver/nextcloud
container_name: nextcloud
environment:
- PUID=1001 #change PUID if needed
- PGID=100 #change PGID if needed
- TZ=Europe/Helsinki
volumes:
- /srv/dev-disk-by-uuid-7763fbc8-15ec-4b11-b010-417a5aaec284/appdata/nextcloud/config:/config
- /srv/dev-disk-by-uuid-7763fbc8-15ec-4b11-b010-417a5aaec284/appdata/nextcloud/data:/data
depends_on:
- mariadb
# ports: # uncomment this and the next line if you want to bypass the proxy
# - 450:443
restart: unless-stopped
mariadb:
image: ghcr.io/linuxserver/mariadb
container_name: nextclouddb
environment:
- PUID=1001 #change PUID if needed
- PGID=100 #change PGID if needed
- MYSQL_ROOT_PASSWORD=[edited]
- TZ=Europe/Helsinki
volumes:
- /srv/dev-disk-by-uuid-7763fbc8-15ec-4b11-b010-417a5aaec284/appdata/nextclouddb:/config
restart: unless-stopped
swag:
image: linuxserver/swag
container_name: swag
cap_add:
- NET_ADMIN
environment:
- PUID=1001 #change PUID if needed
- PGID=100 #change PGID if needed
- TZ=Europe/Helsinki
- URL=[edited]
- SUBDOMAINS=,
- VALIDATION=http
- EMAIL=[edited]
volumes:
- /srv/dev-disk-by-uuid-7763fbc8-15ec-4b11-b010-417a5aaec284/appdata/swag:/config
ports:
- 444:443
- 81:80
restart: unless-stopped
Alles anzeigen
The deployment does eventually finish successfully after the disk has been filled and I can recover by doing a docker system prune --all but it would be nice to know what causes this and how I can prevent it in the future? Should I define a specific image name in "image: ghcr.io/linuxserver/nextcloud" ?