OMV Webgui not reachable

    Do not start docker in this state, it will create new files in / var/lib/docker.


    Can you edit the file /etc/docker/daemon.json to have the correct docker root? This will allow you to start the docker daemon and your docker containers.


    The change will be overwritten by omv on the next apply, so be careful.



    To debug the error, try running omv-salt deploy run on the command line.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    ok I edit the file

    Code
    :/etc/docker# cat /etc/docker/daemon.json
{
  "data-root": "/srv/dev-disk-by-label-med/docker"
}
    Code
    :/# omv-salt deploy run
Usage: omv-salt deploy run [OPTIONS] NAMES...
Try "omv-salt deploy run --help" for help.

Error: Missing argument "NAMES...".

    Sorry, command is omv-salt deploy run omvextras


    and for docker: docker system df I guess the daemon is started by now?

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    Quote from Zoki

    Can you edit the file the json file by hand/etc/docker/daemon.json to have the correct docker root? This will allow you to start the docker daemon and your docker containers.


    The change will be overwritten by omv on the next apply, so be careful.


    If you edit the json file by hand then make sure that System |omv-extras | Docker | Docker root is left blank. So long as it is left blank the edit to the json file will not be overwritten and the path in there will become the Docker root.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

    Like 1
    Quote from Zoki

    systemctl status docker.service

    yes is active:

    Check docker:

    docker system df

    docker ps -a

    docker volume ls

    docker image ls

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    Docker did not pick up you old containers. Doublecheck the path to docker-root and where you moved the directory.

    Stop docker daemon first systemctl stop docker and check if you have new files in /var/lib/docker. Do not copy these again.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    a happy new year at all, thanks for your help last year.

    now we can go on. :)


    I have checked with the follow commands:

    I stoped docker.

    Code
     systemctl status docker.service
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Wed 2022-01-05 09:35:50 CET; 7s ago
     Docs: https://docs.docker.com
  Process: 3336 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=0/SUCCESS)
 Main PID: 3336 (code=exited, status=0/SUCCESS)
    Code
    /var/lib# df -i
Dateisystem                Inodes IBenutzt     IFrei IUse% Eingehängt auf
udev                      2002601      476   2002125    1% /dev
tmpfs                     2008968      820   2008148    1% /run
/dev/sde1                 2883584   169333   2714251    6% /
tmpfs                     2008968        2   2008966    1% /dev/shm
tmpfs                     2008968        3   2008965    1% /run/lock
tmpfs                     2008968       18   2008950    1% /sys/fs/cgroup
tmpfs                     2008968       12   2008956    1% /tmp
/dev/mapper/Stube-Media 169472000  2939394 166532606    2% /srv/dev-disk-by-label-med

    But I can´t change in omv the root of docker.


    Code
    :/var/lib# cat /etc/docker/daemon.json
{
  "data-root": "/srv/dev-disk-by-label-med/docker"
}
    Code
    /var/lib# docker ps -a
CONTAINER ID   IMAGE                     COMMAND        CREATED        STATUS                    PORTS                                                                                  NAMES
e5c2aa0c7046   linuxserver/plex:latest   "/init"        9 months ago   Up 1 second                                                                                                      plex
c40461871d83   portainer/portainer-ce    "/portainer"   9 months ago   Exited (2) 6 months ago   0.0.0.0:8000->8000/tcp, :::8000->8000/tcp, 0.0.0.0:9000->9000/tcp, :::9000->9000/tcp   portainer
    Code
    :/var/lib# docker volume ls
DRIVER    VOLUME NAME
local     portainer_data

:/var/lib# docker image ls
REPOSITORY               TAG       IMAGE ID       CREATED         SIZE
linuxserver/plex         latest    ca1edc33fbe3   9 months ago    680MB
linuxserver/plex         <none>    9c2617e38cc7   10 months ago   680MB
linuxserver/plex         <none>    885ba5181b60   10 months ago   679MB
portainer/portainer-ce   latest    96a1c6cc3d15   11 months ago   209MB
    Code
    :/var/lib# docker image ls
REPOSITORY               TAG       IMAGE ID       CREATED         SIZE
linuxserver/plex         latest    ca1edc33fbe3   9 months ago    680MB
linuxserver/plex         <none>    9c2617e38cc7   10 months ago   680MB
linuxserver/plex         <none>    885ba5181b60   10 months ago   679MB
portainer/portainer-ce   latest    96a1c6cc3d15   11 months ago   209MB

    should I do any next steps?

    • Official Post
    Quote from haemburg2021

    But I can´t change in omv the root of docker.


    Code
    :/var/lib# cat /etc/docker/daemon.json
{
  "data-root": "/srv/dev-disk-by-label-med/docker"
}
    Code
    /var/lib# docker ps -a
CONTAINER ID   IMAGE                     COMMAND        CREATED        STATUS                    PORTS                                                                                  NAMES
e5c2aa0c7046   linuxserver/plex:latest   "/init"        9 months ago   Up 1 second                                                                                                      plex
c40461871d83   portainer/portainer-ce    "/portainer"   9 months ago   Exited (2) 6 months ago   0.0.0.0:8000->8000/tcp, :::8000->8000/tcp, 0.0.0.0:9000->9000/tcp, :::9000->9000/tcp   portainer
    Code
    :/var/lib# docker volume ls
DRIVER    VOLUME NAME
local     portainer_data

:/var/lib# docker image ls
REPOSITORY               TAG       IMAGE ID       CREATED         SIZE
linuxserver/plex         latest    ca1edc33fbe3   9 months ago    680MB
linuxserver/plex         <none>    9c2617e38cc7   10 months ago   680MB
linuxserver/plex         <none>    885ba5181b60   10 months ago   679MB
portainer/portainer-ce   latest    96a1c6cc3d15   11 months ago   209MB
    Code
    :/var/lib# docker image ls
REPOSITORY               TAG       IMAGE ID       CREATED         SIZE
linuxserver/plex         latest    ca1edc33fbe3   9 months ago    680MB
linuxserver/plex         <none>    9c2617e38cc7   10 months ago   680MB
linuxserver/plex         <none>    885ba5181b60   10 months ago   679MB
portainer/portainer-ce   latest    96a1c6cc3d15   11 months ago   209MB

    should I do any next steps?

    Why don't you just change it in the plugin the way it is designed rather than trying to overwrite the docker.json file? I mean either should work if you do it correctly, but you're making this more difficult than it needs to be.

    What are we trying to solve, just get back the old containers? The thread is too long for this evening.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    no, not get back the old container

    I moved the /var/lib/docker to the other disk

    and I changed in the past the daemon.json because I can´t it change in the omv gui and now I don´t know if I have to change it or not

    and now you can see in #92 there is a new folder with docker (probably it is not change in the omv gui)

    If you have a docker container running, you can docker inspect <container_name> to verify which directory it is using now. If it is using

    /srv/dev-disk-by-label-med/docker we need to tell OMV this location. If it is using /var/lib/docker, we need to changethe data-root in daemon.json


    What happens if you put /srv/dev-disk-by-label-med/docker in Docker storage in the UI and press save?

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login