docker.service start failed - Printable Version +- Hilscher Community Forum (https://forum.hilscher.com) +-- Forum: netPI 3 - Docker featuring Industrial Raspberry Pi 3 platform (https://forum.hilscher.com/forum-1.html) +--- Forum: Software (https://forum.hilscher.com/forum-5.html) +--- Thread: docker.service start failed (/thread-550.html) Pages:
1
2
|
RE: docker.service start failed - s.stucchi - January-11th-2021 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. RE: docker.service start failed - Armin@netPI - January-11th-2021 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:
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 RE: docker.service start failed - biancode - January-17th-2021 Hello everyone, We have also Docker problems, with some containers on very new states of the new bought netPI's. Docker Hub Exports have "architecture": "amd64" in their JSON config and "io.balena.architecture": "armv7hf" - maybe that should be aarch64 or arm64? ( V1.2.2.0 ) The from the netPI exported image is seen as an amd64 architecture from other tests on RPI3 and wont work well. see 78f6ab1d8d9a237a63aa4f12452bdbce0250730523c3ec616d803382ac019aef.json - inside the netPI Node-RED's image.tar I have the problem again, a fresh installed Hilscher netPI even with original card dies after a few days of running the Docker service and Docker does not start anymore. A reset via USB-Stick helps, but some crashes the Docker Service over time again with a lot of cgroup errors in the syslog as I sent to Armin. Problem of amd64 is on - directly export from netPI (v1.2.2 Barcode end number 2 very new devices and images from docker as well)
The OpenVPN is OK and shows arm architecture.
RE: docker.service start failed - Armin@netPI - January-17th-2021 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 |