Posts by DNUKaen

Quote from gderf

There is at least one other thread that appeared today related to this. Have you read them yet?

Yeah a few hours ago - I have downgraded and resolved the issue and have put hold on the updates showing - Im back to this and its working

docker version

Client: Docker Engine - Community

 Version:           28.5.2

 API version:       1.51

 Go version:        go1.25.3

 Git commit:        ecc6942

 Built:             Wed Nov  5 14:43:25 2025

 OS/Arch:           linux/amd64

 Context:           default

Server: Docker Engine - Community

 Engine:

  Version:          28.5.2

  API version:      1.51 (minimum version 1.24)

  Go version:       go1.25.3

  Git commit:       89c5e8f

  Built:            Wed Nov  5 14:43:25 2025

  OS/Arch:          linux/amd64

  Experimental:     false

 containerd:

  Version:          v2.1.5

  GitCommit:        fcd43222d6b07379a4be9786bda52438f0dd16a1

 runc:

  Version:          1.3.3

  GitCommit:        v1.3.3-0-gd842d771

 docker-init:

  Version:          0.19.0

  GitCommit:        de40ad0

I have just done an update and once OMV Rebooted Docker is Down and cant get it restarted. Ive checked portainer which opens but shows Dockers are down. Is there a way to reinstall the update and run again or is there a problem with the update? How do I get Docker Running again

Thanks in advance for any help

sudo systemctl restart docker

Job for docker.service failed because the control process exited with error code.

See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.

I then try that and get this

systemctl status docker.service

× docker.service - Docker Application Container Engine

Loaded: loaded (/lib/systemd/system/docker.service; enabled; preset: enabled)

    Drop-In: /etc/systemd/system/docker.service.d

             └─waitAllMounts.conf

Active: failed (Result: exit-code) since Tue 2025-11-11 23:40:34 GMT; 5min ago

TriggeredBy: × docker.socket

       Docs: https://docs.docker.com

Process: 46366 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=2)

   Main PID: 46366 (code=exited, status=2)

        CPU: 17ms

What can I do to sort this out? Ive tried a reinstall via the GUI for OMV. It hasnt worked. Is there a way to use a backup or to completely remove and reinstall

Quote from ryecoaaron

The reinstall docker button in the compose plugin does that. Give it a shot. You won't lose anything.

This didnt stop the same error happening

If I backup my appdata folder and then look to use terminal to completely remove docker and then reinstall would this work?

If I do that is there a certain way I should remove and certain way to reinstall Docker for OMV via Terminal

Quote from ryecoaaron

I don't know what else to try since I think this is a network issue. Maybe try restarting your router. Otherwise, I don't have any other ideas.

I will try a router restart and see but if I have internet would that be the problem?

What would be the best way forward if nothing works? Can I remove Docker completely and reinstall but keep the configs for all my containers?

I have tried this

sudo systemctl restart network-manager

Failed to restart network-manager.service: Unit network-manager.service not found.

Quote from ryecoaaron

docker pull nginx

~/appdata/overseeing$ docker pull nginx

Using default tag: latest

Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: TLS handshake timeout

Quote from ryecoaaron

journalctl -u docker --no-pager | tail -50

~/appdata/overseeing$ journalctl -u docker --no-pager | tail -50

Hint: You are currently not seeing messages from other users and the system.

Users in groups 'adm', 'systemd-journal' can see all messages.

Pass -q to turn off this notice.

-- No entries --

Quote from ryecoaaron

Have you tried restarting docker or the system?

I have restarted Docker and also rebooted the server with no change when I pull request

Quote from ryecoaaron

docker pull ghcr.io/linuxserver/tautulli

~/appdata/overseeing$ docker pull ghcr.io/linuxserver/tautulli

Using default tag: latest

Error response from daemon: Get "https://ghcr.io/v2/": net/http: TLS handshake timeout

Thats what returned

~/appdata/overseeing$ nslookup ghcr.io

bash: nslookup: command not found

Quote from ryecoaaron

docker pull nginx[/tt

[tt]journalctl -u docker --no-pager | tail -50

Do you have ipv6 enabled in docker?

I have no idea if its enabled as it all was working fine before. The above docker pull not sure what to do with that?

Yes I did and I get the same back

docker compose pull

WARN[0000] /home/biniazd/appdata/overseeing/docker-compose.yaml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion

[+] Pulling 2/2

✘ overseerr Error Get "https://ghcr.io/v2/": net/http: TLS handshake timeout 10.1s

✘ tautulli Error Get "https://ghcr.io/v2/": net/http: TLS handshake timeout 10.1s

Error response from daemon: Get "https://ghcr.io/v2/": net/http: TLS handshake timeout

As you can see I used the docker compose pull and no change

All the images I have will not pull. Overserr and Tautulli whist they will not pull I can still access. I have tried to add the others using Portainer but this didnt work either. I have the trashguides one in a long stack that has been working up to the updating of OMV

I recently updated OMV as I had lots of updates needed. After this completed I have been unable to get my Docker via CLI to pull. I have restarted Docker and this hasnt worked. When I pull I get the below errors

docker-compose pull

[+] Pulling 7/7

✘ kometa Error Get "https://ghcr.io/v2/": net/http: TLS handshake timeout 10.0s

✘ sports-organizer Error Get "https://ghcr.io/v2/": net/http: TLS handshake timeout 10.0s

✘ prowlarr Error Get "https://ghcr.io/v2/": net/http: TLS handshake timeout 10.0s

✘ recyclarr Error Get "https://ghcr.io/v2/": net/http: TLS handshake timeout 10.0s

✘ qbittorrentwgvpn Error Get "https://ghcr.io/v2/": net/http: TLS handshake timeout 10.0s

✘ radarr Error Get "https://ghcr.io/v2/": net/http: TLS handshake timeout 10.0s

✘ sonarr Error Get "https://ghcr.io/v2/": net/http: TLS handshake timeout 10.0s

Error response from daemon: Get "https://ghcr.io/v2/": net/http: TLS handshake timeout

I have been informed that this could be a network issue but when I ping from my server it pings fine

--- google.com ping statistics ---5 packets transmitted, 5 received, 0% packet loss, time 4006msrtt min/avg/max/mdev = 2.341/2.558/2.661/0.116 ms

Any help to get this sorted would be amazing

This has been resolved - It was the GID & UID in the docker compose was not correct

I updated OMV yesterday and now some of my dockers arent working. Qbt is not downloading content and shows errored also Immich isnt working.

Ive added screenshots of what I have checked but need help understanding if the permissions are correct for the folder where the torrents are downloaded to

I have had a new 3 Gigabit internet service installed with a new ISP router but I am unable to add a Static IP Address or change the Local Network IP Address to match what I had before and what is on OMV.

Im wondering how to change this if its possible to do so on OMV? Also I would need to change my Docker containers and wondering what else would need to be changed to ensure everything works as it did

I'm still having the same problem.

I have put everything back to the way it was and still getting MAX 20mb transfer speeds on the OMV server. The server as I said has a 2.5G card in it and is setup correctly. I also have a 2.5G switch.

I have tried updating OMV and also rebooting but still the same speeds.

I'm wondering if the change in router has caused a problem - the new router has a minimum 1gb ethernet connection that my switch is connected to - so I should be getting faster speeds

Ive upgraded to

Version
7.4.17-2 (Sandworm)

SMB is working but so slow. I have had new internet package installed which Im not sure might effect it. I have a 2.5G Card and switch which also seems like its not running either

Any help much appreciated

Ive downloaded the syslog and tried to add the file here but its to long how would I do this so you can have a look

Quote from ryecoaaron

You haven't given me any more info like hardware details. Have you looked at the Physical disks tab to see if a disk is having problems?

Ive checked in SMART - Devices and all disks are showing GOOD

Quote from ryecoaaron

That doesn't tell us anything. You need to copy and paste from the Bell in the top right of the web interface to get the full error message.

As it started working again I have deleted the notifications sorry.