January-11th-2021, 10:00 AM
The same problem for me today. This is bad.
How can i restore the file content without reflash firmware?
Thanks
---Edit---
Problem Solved!
I attach the internal sd to a computer and after editing the files and reboot all works well.
For me the ssh service is essential for this type of problems. Is there a way to enable it from the web-gui?
Thanks.
January-11th-2021, 01:16 PM
(This post was last modified: January-11th-2021, 01:36 PM by Armin@netPI.)
Hi there,
good to hear that you find a way yourself to solve problem and to recover the deleted docker conf.file. This is a good idea by the way.
I am sorry to say that SSH was not an option from the beginning when netPI product was defined 5 years ago. Even if you would have access to the Linux host over SSH you can't do anything with it since it is a secured Linux and just installs signed HIlscher packages only and never any packages from the web.
These are the one and only options:
- You can of course deploy a container that includes SSH ... but then this SSH will get access to the internals of the container ... never to the host Linux. For example this one: https://hub.docker.com/r/hilschernetpi/netpi-raspbian
- Also you can open the netPI device housing by unscrewing the screws, remove the included Hilscher OS SD card and put it aside and use then the netPI with an own SD card and Raspbian OS. Then you have all possibilities and you own choice.
The docker service start problem was solved in the system software version V1.2.2.0 by the way. So even if you have corrected the problem yourself, I strongly recommend to update to version V1.2.2.0
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
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:
Code:
unable to configure the Docker daemon with file /etc/docker/daemon.json: EOF
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
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)