Relocating the Docker root directory docker does not start

Docker Hub
1

I change my docker directory.
But now the docker.socket could not start.

to change the directory i use this Manual:
https://www.ibm.com/docs/en/z-logdata-analytics/5.1.0?topic=compose-relocating-docker-root-directory

the new directory (/var/docker) was created as seperate Volumes with LVM

this is my /etc/docker/daemon.json file:

{
 "data-root": "/var/docker/docker"
}
{
        "log-driver": "json-file",
        "log-level": "",
        "log-opts": {
                "cache-disabled": "false",
                "cache-max-file": "5",
                "cache-max-size": "20m",
                "cache-compress": "true",
                "env": "os,customer",
                "labels": "somelabel",
                "max-file": "5",
                "max-size": "10m"
  }
}

the System:

lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

Docker Version:

sudo docker version
Client: Docker Engine - Community
 Version:           23.0.5
 API version:       1.42
 Go version:        go1.19.8
 Git commit:        bc4487a
 Built:             Wed Apr 26 16:17:45 2023
 OS/Arch:           linux/amd64
 Context:           default
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

I get this stats

sudo systemctl status docker
● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Fri 2023-05-05 11:00:18 EEST; 20min ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
    Process: 558 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, stat>
   Main PID: 558 (code=exited, status=1/FAILURE)
        CPU: 43ms

May 05 11:00:16 AGstDocker systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
May 05 11:00:16 AGstDocker systemd[1]: docker.service: Failed with result 'exit-code'.
May 05 11:00:16 AGstDocker systemd[1]: Failed to start Docker Application Container Engine.
May 05 11:00:18 AGstDocker systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
May 05 11:00:18 AGstDocker systemd[1]: Stopped Docker Application Container Engine.
May 05 11:00:18 AGstDocker systemd[1]: docker.service: Start request repeated too quickly.
May 05 11:00:18 AGstDocker systemd[1]: docker.service: Failed with result 'exit-code'.
May 05 11:00:18 AGstDocker systemd[1]: Failed to start Docker Application Container Engine.


sudo systemctl status docker.socket
● docker.socket - Docker Socket for the API
     Loaded: loaded (/lib/systemd/system/docker.socket; enabled; vendor preset: enabled)
     Active: failed (Result: service-start-limit-hit) since Fri 2023-05-05 11:00:18 EEST; 22min ago
   Triggers: ● docker.service
     Listen: /run/docker.sock (Stream)
        CPU: 496us

May 05 11:00:10 AGstDocker systemd[1]: Starting Docker Socket for the API.
May 05 11:00:10 AGstDocker systemd[1]: Listening on Docker Socket for the API.
May 05 11:00:18 AGstDocker systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.

How can i fix it?

Thanks for help

2

Try:

{
        "data-root": "/var/docker/docker",
        "log-driver": "json-file",
        "log-level": "",
        "log-opts": {
                "cache-disabled": "false",
                "cache-max-file": "5",
                "cache-max-size": "20m",
                "cache-compress": "true",
                "env": "os,customer",
                "labels": "somelabel",
                "max-file": "5",
                "max-size": "10m"
        }
}

I didn’t check the settings, I just joined your two json documents to a single document. I am not sure if “log-level” really works with an empty string value.

3

meyan thanks for your help.

the Problem was the settings of the log-driver.
I delete the complete log config.
Now works

Thanks