January-17th-2021, 07:52 PM
Hello Biancode,
the Docker start problem corrected in version 1.2.2.0 relates back to an empty daemon.json. It is caused by a Linux file system synch problem not writing the file physically to the SD card and leaving the touched file empty.
During the next start of the device the Docker Daemon fails to start since the file is empty. Devices in thie state indicate the following error in the log file:
In the log files you sent to me via private messages in none of these I was able to see the error above. So your problem does not relate to the problems all the others have in this thread. In you log file whereas I see a lot of other things not starting and the root cause it not known right now and needs in-deep examination.
It would be nice to open a new thread with a new syslog file that shows your problem if it occurs again. I would be also nice to get a list of all the containers you are using while the error occurs.
Thx
Armin
the Docker start problem corrected in version 1.2.2.0 relates back to an empty daemon.json. It is caused by a Linux file system synch problem not writing the file physically to the SD card and leaving the touched file empty.
During the next start of the device the Docker Daemon fails to start since the file is empty. Devices in thie state indicate the following error in the log file:
Code:
unable to configure the Docker daemon with file /etc/docker/daemon.json: EOFIn the log files you sent to me via private messages in none of these I was able to see the error above. So your problem does not relate to the problems all the others have in this thread. In you log file whereas I see a lot of other things not starting and the root cause it not known right now and needs in-deep examination.
It would be nice to open a new thread with a new syslog file that shows your problem if it occurs again. I would be also nice to get a list of all the containers you are using while the error occurs.
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
