Four Docker containers suddenly stopped working

Zitat von Soma

muchgooder

Found the easiest procedure:

OMV on Raspberry and SD Card full! - General - openmediavault

Read that post and the few ones after to get a better understanding on it,

And another:

Beitrag

RE: Upgrade from OMV 5 to OMV 6 and docker

[…]

Yes, it is. I've only done this on amd64's with SATA drives, but I can't imagine the procedure and end result is much different.

1. SSH your server and become root.
2. Stop docker

(Quelltext, 1 Zeile)

3. cd /var/lib
4. We'll copy the docker folder just in case something goes wrong... (I would not recommend making this a subdirectory of other directories, sharing over SMB, etc.. as docker puts some pretty harsh permissions on this folder... so I'd just put it right under the UUID by itself…

KM0201

5. September 2022

Alles anzeigen

I can't tell you how much I appreciate your help! I read through everything and it makes complete sense. I am copying over the files now but unfortunately I suspect that the health of the drive is hurting me.

I seem stuck on a specific overlay2. I've spent the last hour trying to delete it - I could not figure out a way to do it. Every command threw at it resulted in some kind of error (drive is read-write, can't change permissions, etc). I then stumbled onto e2fsk commands - they all dutifully reported that there was an error and that it couldn't continue. Is there anything else I can do? Or is the drive most likely causing the issue?

Zitat von Soma

You can try to exclude that folder.

Thanks so much - all of this has really allowed me to fill in some areas that I was missing. I have been going through each config folder to issue docker-compose up on the yml files. Most have reconfigured themselves without issue but some are causing a problem. Mariadb is one of them.

version: '3.1'


services:


mariadb:
image: mariadb
restart: unless-stopped
container_name: mariad
volumes:
- /srv/dev-disk-by-label-HOMEMEDIA/AppData/Mariadb:/var/lib/mysql
environment:
MARIADB_AUTO_UPGRADE: "1"
MARIADB_INITDB_SKIP_TZINFO: "1"
MARIADB_DATABASE: "photoprism"
MARIADB_USER: "xbmc"
MARIADB_PASSWORD: "xbmc"
MARIADB_ROOT_PASSWORD: "redacted"
ports:
- 3306:3306

I had this one running previously but it is giving me an error now when I tried to re-initialize it. Any ideas?

EDIT - it is happening with a couple of other containers as well. There is still a bit of knowledge that I am missing here - I had thought that running docker compose again would fill in anything that was broken? Obviously this is incorrect.

Zitat von muchgooder

Thanks so much - all of this has really allowed me to fill in some areas that I was missing. I have been going through each config folder to issue docker-compose up on the yml files. Most have reconfigured themselves without issue but some are causing a problem. Mariadb is one of them.

Code

version: '3.1'


services:


mariadb:
image: mariadb
restart: unless-stopped
container_name: mariad
volumes:
- /srv/dev-disk-by-label-HOMEMEDIA/AppData/Mariadb:/var/lib/mysql
environment:
MARIADB_AUTO_UPGRADE: "1"
MARIADB_INITDB_SKIP_TZINFO: "1"
MARIADB_DATABASE: "photoprism"
MARIADB_USER: "xbmc"
MARIADB_PASSWORD: "xbmc"
MARIADB_ROOT_PASSWORD: "redacted"
ports:
- 3306:3306

Alles anzeigen

I had this one running previously but it is giving me an error now when I tried to re-initialize it. Any ideas?

EDIT - it is happening with a couple of other containers as well. There is still a bit of knowledge that I am missing here - I had thought that running docker compose again would fill in anything that was broken? Obviously this is incorrect.

Alles anzeigen

I am going to close this particular issue as the root issue was solved (bad disk). I have most other containers running again but a few are giving me an issue.