Containers stopped running

vandoe · 24. Februar 2022

I just discovered that my containers just stopped running. I had Nextcloud, Bitwarden and wireguard all running fine. The only thing done to the system was to add an additional hardrive to my NAS. The NAS is working fine. I can access all the data on the disks just fine. running docker ps -a also shows no containers at all. I ran a test case where I reloaded my wireguard stack using portainer and it errored out. Below is the error message:

Code

Deployment error
failed to deploy a stack: Error response from daemon: layer does not exist

Any thoughts on how to recover?

Soma · 24. Februar 2022

Post the YMLs/stack used to see where your volumes are configured.

Also:

mount | grep disk

lsblk

blkid

Zoki · 24. Februar 2022

and cat /etc/docker/daemon.json to see, where docker expects its stuff.

vandoe · 24. Februar 2022

Here is the nextcloud/bitwarden stack:

Code

version: "2"
services:
  nextcloud:
    image: ghcr.io/linuxserver/nextcloud:latest
    container_name: nextcloud
    environment:
      - PUID=1000
      - PGID=100
      - TZ=America/New_York
    volumes:
      - /srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Docker-Config/nextcloud/:/config
      - /srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Primary/AppData/Nextcloud/:/data
    depends_on:
      - nextclouddb
    ports:
      - 450:443
    restart: unless-stopped
  nextclouddb:
    image: ghcr.io/linuxserver/mariadb:latest
    container_name: nextclouddb
    environment:
      - PUID=1000
      - PGID=100
      - MYSQL_ROOT_PASSWORD=dbpassword
    volumes:
      - /srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Docker-Config/nextclouddb/:/config
    restart: unless-stopped
  swag:
     image: linuxserver/swag
     container_name: swag
     cap_add:
      - NET_ADMIN
     environment:
      - PUID=1000
      - PGID=100
      - TZ=America/New_York
      - DNSPLUGIN=duckdns
      - URL=duckdns.org
      - DUCKDNSTOKEN=mytoken
      - SUBDOMAINS=mmydomainnextcloud,mydomainbitwarden
      - ONLY_SUBDOMAINS=true
      - VALIDATION=http
      - EMAIL=myemail
     volumes:
      - /srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Docker-Config/swag/:/config
     ports:
      - 444:443
      - 81:80
     restart: unless-stopped
  bitwarden:
     image: bitwardenrs/server:latest # raspberry
     container_name: bitwarden
     volumes:
      - /srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Docker-Config/bitwarden/:/config
     ports:
      - 8005:80
     restart: unless-stopped

Alles anzeigen

vandoe · 24. Februar 2022

Here are the other requested items:

mount | grep disk

Code

/dev/sdc1 on /srv/dev-disk-by-uuid-f1ebbf1b-0cc5-4056-bba0-0e4f7e08932d type ext4 (rw,relatime,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group)
overlay on /srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Docker/overlay2/d4f7cef45dbdef46192655e7b192cb212c36a882937aae6f4055cd4253c3ff7e/merged type overlay (rw,relatime,lowerdir=/srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Docker/overlay2/l/JKBQWOYQ2AAMKCRISZLQQWHG4T:/srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Docker/overlay2/l/6YUF322H3FUPXQZBCMCHTVCQQM:/srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Docker/overlay2/l/TWMRF3GZ4J3ZNTPUL2OL725DBD:/srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Docker/overlay2/l/O7IBVJB3YXYNCCQVIRELLLKLR6,upperdir=/srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Docker/overlay2/d4f7cef45dbdef46192655e7b192cb212c36a882937aae6f4055cd4253c3ff7e/diff,workdir=/srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Docker/overlay2/d4f7cef45dbdef46192655e7b192cb212c36a882937aae6f4055cd4253c3ff7e/work)
/dev/sda1 on /srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f type ext4 (rw,relatime,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group)

lsblk

Code

           8:0    0   1.8T  0 disk
└─sda1        8:1    0   1.8T  0 part /srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f
sdb           8:16   0 111.8G  0 disk
└─sdb1        8:17   0 111.8G  0 part /srv/dev-disk-by-uuid-12E426FAE426E029
sdc           8:32   0   1.4T  0 disk
└─sdc1        8:33   0   1.4T  0 part /srv/dev-disk-by-uuid-f1ebbf1b-0cc5-4056-bba0-0e4f7e08932d
mmcblk0     179:0    0  29.7G  0 disk
├─mmcblk0p1 179:1    0   256M  0 part /boot
└─mmcblk0p2 179:2    0  29.5G  0 part /
span id="selection-marker-1" class="redactor-selection-marker woltlab-bbcode-marker"></span>

blkid

Code

/dev/mmcblk0p1: LABEL_FATBOOT="boot" LABEL="boot" UUID="DC3E-E470" TYPE="vfat" PARTUUID="5feefdba-01"
/dev/mmcblk0p2: LABEL="rootfs" UUID="a7adb26a-8b87-4729-99c8-9f5ac069d51e" TYPE="ext4" PARTUUID="5feefdba-02"

cat /etc/docker/daemon.json

Code

"data-root": "/srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Docker"

Soma · 25. Februar 2022

Your docker drive show's it's mounted so it should be OK.

Can you try to check the status/restart the docker service or maybe reboot the PC:

sudo systemctl status docker.service

sudo systemctl restart docker.service

sudo reboot now

vandoe · 25. Februar 2022

Zitat von Soma

sudo systemctl restart docker.service

This seems to have restarted all my containers. Thank you

vandoe · 26. Februar 2022

After getting the containers up and running everything works except I can't access anything through wireguard.

Zitat von Wireguard guide

We can check it by opening a browser and accessing the IP of any service on our LAN.T he home network appears on the screen, we press the button on the right and we give it permission to access.

I should be able to open openmediavault by putting in 192.168.0.23:85 from a browser according to the above. This did not work for me. I was able to get to my files originally by setting up a remote connection in my android file browser with SFTP using IP 192.168.0.23 and port 22. After restart this does not work either

Containers stopped running

Jetzt mitmachen!

Ähnliche Themen

omv-extras plugins - porting progress to OMV 6.x (done)

Openmediavault disk mount fail Error#0

Uninstall Filecloud [Solved]

Docker Stacks

Hard drive constantly emitting "working" noise