I would like to try to clean out the container runtime storage on device. that would make it pull the images again. would you be ok with that (asking in case the device is not on lan/wifi)
sure, the device is on Wifi. go ahead
Hi there! It seems that support access is expired. If you extend the support access on this device weâll be happy to work on that.
In case youâd like to work on the troubleshooting I can give you some instructions on how to proceed. Please notice that this action will delete every image and any container that ever ran and any data associated with the container engine. This way the supervisor will be forced to download all images again.
You can either ssh to the device or use the terminal from your dashboard and run the following commands:
systemctl stop resin-supervisor
systemctl stop docker
rm -rf /var/lib/docker/{aufs,overlay,containers,image,tmp}
systemctl start docker
update-resin-supervisor
Please let me know how it works for you or confirm the support access.
sorry i extended the support access of course !
Hi, unfortunately we tried the cleansing operations above but the device did not come back to a functional state. Both engine and supervisor started successfully and the supervisor started to re-download the application. We then lost connectivity when the application was around a 50% downloaded. At the moment the device is not reachable. Would it be possible for you to reboot the device see if we can gain access again?
it doesnt come back online on the dashboardâŚshould i reflash it ?
Hi, from the thread history we know that if you re-flash it will work initially and fail on a subsequent boot. I am thinking that something that might give us a clue is if you preload the image with the application as explained in https://www.balena.io/docs/reference/balena-cli/#preload-image. We can then see whether the first boot works or not.
ok, i saw now that it came back up. i will wait until its done and if this doesnt work i will go after your link
Whomever is coming upon this set of commands in the future, please exercise caution when attempting them as this will result in data loss and may have unintended consequences. It is meant as a ânuke everythingâ option when no other debug attempt works. Instead, please make a post in forums or our paid support and balena support agents or the community will attempt to help.
If you must use the command though, the correct command sequence is as below:
systemctl stop balena-supervisor
systemctl stop balena
rm -rf /var/lib/docker/{aufs,overlay2,containers,image,tmp}
systemctl start balena
update-balena-supervisor
Corrected typo overlay
â overlay2
.
Replace balena
with resin
if you have an older OS. To verify whether resin
or balena
works, run the first command only and view the results. If it errors, replace balena with resin.