docker.service start failed

[Armin@netPI]

I have seen such an effect myself already.

What I did was just unpowering my netPI instead of shutting it down properly using the "shutdown" function in the control panel. To be honest I am doing this always by just removing the 24V power, but this time it seems to corrupted my netPI file system.

The system log file was showing me something like that

Code:

<37>1 2020-07-20T07:56:15+00:00 ab-lte-netpi audit 1750 - - SYSCALL arch=40000028 syscall=322 per=800000 success=yes exit=6 a0=ffffff9c a1=139c14a0 a2=a0000 a3=0 items=1 ppid=1 pid=1750 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="dockerd" exe="/usr/bin/dockerd" key="docker"
<37>1 2020-07-20T07:56:15+00:00 ab-lte-netpi audit - - - CWD cwd="/"
<37>1 2020-07-20T07:56:15+00:00 ab-lte-netpi audit - - - PATH item=0 name="/etc/docker/daemon.json" inode=8820 dev=00:13 mode=0100644 ouid=0 ogid=0 rdev=00:00 nametype=NORMAL
<37>1 2020-07-20T07:56:15+00:00 ab-lte-netpi audit - - - PROCTITLE proctitle=2F7573722F62696E2F646F636B657264002D480066643A2F2F
<30>1 2020-07-20T07:56:15+00:00 ab-lte-netpi dockerd 1750 - - unable to configure the Docker daemon with file /etc/docker/daemon.json: EOF
<29>1 2020-07-20T07:56:15+00:00 ab-lte-netpi systemd 1 - - docker.service: Main process exited, code=exited, status=1/FAILURE
<27>1 2020-07-20T07:56:15+00:00 ab-lte-netpi systemd 1 - - Failed to start Docker Application Container Engine.
<37>1 2020-07-20T07:56:15+00:00 ab-lte-netpi audit 1 - - SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
<29>1 2020-07-20T07:56:15+00:00 ab-lte-netpi systemd 1 - - docker.service: Unit entered failed state.
<28>1 2020-07-20T07:56:15+00:00 ab-lte-netpi systemd 1 - - docker.service: Failed with result 'protocol'.
<30>1 2020-07-20T07:56:16+00:00 ab-lte-netpi systemd 1 - - docker.service: Service hold-off time over, scheduling restart.

so the docker daemon reports that it can't be started cause the daemon.json file got corrupt.

And indeed ... I have a very special netPI where I was able to look to the host's file system and to th /etc/docker/deamon.json file and I saw that it was totally empty which I cannot explain why.

Usually this file content is  

Code:

{
 "storage-driver": "overlay2",
 "data-root": "/run/.system_part/docker",
 "live-restore": true,
 "disable-legacy-registry": true,
 "userland-proxy": false,
 "userland-proxy-path": "/usr/bin/docker-proxy",
 "log-driver": "journald"
}

So I really have no clue where this effect was coming from other than I removed the power from the netPI device instantly.