September-19th-2018, 11:07 AM
Jonas, I just continued my tests with the reset command
I filled my netPI SD card by 100% writing a big file to it using the command
dd bs=1024 count=10000000 </dev/urandom >outputfile
Even though my netPI was still accessible accross the web interface.
Then I called the special reset command, netPI rebooted but wasn't able to start any container any more cause of missing disk space.
I know it is not your error scenario, but interesting to see that missing disk space causes Docker not to start any container any more.
Then you confirmed "no linux" command can be called any more in the bluetooth container. So not even the important "dmesg" command that lists you important log entries can't be called any more? I know you can't tell it today since your netPI is down ... but maybe in future.
Thx
I filled my netPI SD card by 100% writing a big file to it using the command
dd bs=1024 count=10000000 </dev/urandom >outputfile
Even though my netPI was still accessible accross the web interface.
Then I called the special reset command, netPI rebooted but wasn't able to start any container any more cause of missing disk space.
I know it is not your error scenario, but interesting to see that missing disk space causes Docker not to start any container any more.
Then you confirmed "no linux" command can be called any more in the bluetooth container. So not even the important "dmesg" command that lists you important log entries can't be called any more? I know you can't tell it today since your netPI is down ... but maybe in future.
Thx
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
