docker graphic driver error

tannaroo · Feb 1st 2025

Hi

I booted up my omv test unit running on a pi. after a lot of updates, my portainer is not working and i think I have tracked the error. Is this the issue and how can I fix it?

Code

 sudo dockerd --debug
INFO[2025-02-01T11:22:36.376087240Z] Starting up
DEBU[2025-02-01T11:22:36.381220096Z] Listener created for HTTP on unix (/var/run/docker.sock)
INFO[2025-02-01T11:22:36.383362154Z] OTEL tracing is not configured, using no-op tracer provider
INFO[2025-02-01T11:22:36.384371881Z] detected 127.0.0.53 nameserver, assuming systemd-resolved, so using resolv.conf: /run/systemd/resolve/resolv.conf
DEBU[2025-02-01T11:22:36.450990260Z] Golang's threads limit set to 4500
DEBU[2025-02-01T11:22:36.453262161Z] metrics API listening on /var/run/docker/metrics.sock
DEBU[2025-02-01T11:22:36.484187576Z] Using default logging driver json-file
DEBU[2025-02-01T11:22:36.485644330Z] No quota support for local volumes in /srv/dev-disk-by-uuid-392f8822-81cd-443e-932e-af25089b5b08/appdata/docker/volumes: Filesystem does not support, or has not enabled quotas
DEBU[2025-02-01T11:22:36.486449633Z] processing event stream                       module=libcontainerd namespace=plugins.moby
DEBU[2025-02-01T11:22:36.506351273Z] [graphdriver] priority list: [overlay2 fuse-overlayfs btrfs zfs vfs]
ERRO[2025-02-01T11:22:36.527461648Z] failed to mount overlay: no such device       storage-driver=overlay2
ERRO[2025-02-01T11:22:36.527712687Z] [graphdriver] prior storage driver overlay2 failed: driver not supported
DEBU[2025-02-01T11:22:36.527801436Z] daemon configured with a 15 seconds minimum shutdown timeout
DEBU[2025-02-01T11:22:36.528216431Z] start clean shutdown of all containers with a 15 seconds timeout...
DEBU[2025-02-01T11:22:36.533159966Z] Cleaning up old mountid : start.
DEBU[2025-02-01T11:22:36.535531396Z] Cleaning up old mountid : done.
failed to start daemon: error initializing graphdriver: driver not supported

Display More

chente · Feb 1st 2025

Have you installed docker on a ZFS or BTRFS filesystem?

tannaroo · Feb 1st 2025

Quote from chente

Have you installed docker on a ZFS or BTRFS filesystem?

Its EXT4 filesystem

chente · Feb 1st 2025

How did you install Portainer? Are you using the compose plugin?

tannaroo · Feb 1st 2025

Quote from chente

How did you install Portainer? Are you using the compose plugin?

I cant actually remember as it was year or two ag but pretty sure not the compose plugin (as don't know what that is)

chente · Feb 1st 2025

Ok, I think I see the problem now. I didn't notice the OMV6 tag. You probably installed Portainer from the omv-extras GUI when that option was still offered. You must carry out this process: https://wiki.omv-extras.org/do…openmediavault-compose_67

After that I recommend you upgrade to OMV7, OMV6 is EOL.

tannaroo · Feb 1st 2025

ok thanks. though i am now getting gateway errors so i think i have another problem

chente · Feb 1st 2025

I guess you'll have to fix one problem after another, but what errors are you getting? can you publish them?

tannaroo · Feb 1st 2025

Quote from chente

I guess you'll have to fix one problem after another, but what errors are you getting? can you publish them?

Code

500 - Internal Server Error
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; export DEBIAN_FRONTEND=noninteractive; apt-get --yes --allow-downgrades --allow-change-held-packages --fix-broken --fix-missing --auto-remove --allow-unauthenticated --show-upgraded --option DPkg::Options::="--force-confold" dist-upgrade 2>&1' with exit code '100': E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.

I ran dpkg --configure -a which seemed to fix it and was working.

After, I installed the updates and now I get the same error as above.

chente · Feb 1st 2025

Quote from tannaroo

After, I installed the updates and now I get the same error as above.

You don't give many details. I'm not in front of your PC, I can't see what you do and what you receive.

tannaroo · Feb 1st 2025

I following this process: https://wiki.omv-extras.org/do…openmediavault-compose_67

It does not work for me on these steps:

Press the Up button
- If it gives an error, you may have to reinstall docker. In Services > Compose > Settings Click on the Reinstall Docker button and click Up button again.
Now your Portainer container is working exactly the same as you had it and you can manage your containers from Portainer just like before.

So I press Up button and get an error message. So I reinstall Docker (confirmed its insallled and running) and try the Up button but I get an error message.

Code

500 - Internal Server Error
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; docker compose --file '/srv/dev-disk-by-uuid-392f8822-81cd-443e-932e-af25089b5b08/appdata/portainer/portainer.yml' --file "/srv/dev-disk-by-uuid-392f8822-81cd-443e-932e-af25089b5b08/appdata/portainer/compose.override.yml" --env-file '/srv/dev-disk-by-uuid-392f8822-81cd-443e-932e-af25089b5b08/appdata/global.env' --env-file '/srv/dev-disk-by-uuid-392f8822-81cd-443e-932e-af25089b5b08/appdata/portainer/portainer.env' up -d 2>&1': external volume "portainer_data" not found

tannaroo · Feb 1st 2025

I think I fixed it but my existing containers are not there.

docker graphic driver error

Participate now!

Similar Threads

NFS issue after upgrade to RC1

Dual GPU configuration error

NVIDIA Container Toolkit - installation Error on OMV6