Using Docker causes multiple system crash and eventually Fails to Boot

So I am using Docker to build ARM64 applications natively on the Axon system.
To save space I am storing the cache in an SD card, a SanDisk Extreme 64GB U3 A2 microXC V30.
The system was working fine for a while, then it started to crash after some time whenever Docker.service started .
I thought it was due to high RAM usage, so I avoided using the browser while running the Docker.
The crashes become frequent. Now the system is not working at all .
The white light stays still, It’s not blinking.

I also tried to reflash the image, but that approch also not working , alas i am getting a segmentation error .

sudo ./upgrade_tool ld

List of rockusb connected (1)

DevNo=1 Vid=0x2207, Pid=0x350b, LocationID=12

Mode Maskrom

SerialNo=

sudo ./upgrade_tool uf ubut.....

Loading firmware...

Support Type: 3588

FW Ver:1.0.00

FW Time: 2025-03-04

12:46:33

Loader ver:1.0b Loader

Time: 2025-03-03

10:38:52

Segmentation fault

I heard (but I’m not sure) frequent reading and writing can cause issues for the system. I checked the SD card; it’s a working file.

Using charger Zebronics RC45A C 45 W PD .



Anyone suggest a good UART cable for Axon. Mine was not of good quality

To debug your issue :

Could you answer some of the questions that we have?

  • In what method do you have installed Docker, like, using our guide, which is given in Docker Setup | Vicharak?
  • What is the image and kernel that you are using with the kernel time stamp?
  • I hope you have not run any command that ultimately changes boot partition and U-Boot file, which should be in a particular location ?

You can use normal usb to type-c cable.
https://www.amazon.in/Ambrane-RCT-10-Cable-Black/dp/B0CJJQLDS9/ref=sr_1_5?sr=8-5&th=1

USB To Type-C
CH340C IC

1 > I used the same method mentioned in the document
2 > I was using rockay9 image and using latest kernel
3 > i am not touching anything related to boot partition or uboot

https://hub.docker.com/layers/library/rockylinux/9/images/sha256-370b6bd1851d5023c5c673535c85cdc5c1d8a59416ad83380a8db7ce3691bd45

Yes, basically you can not access the whole system, including the U-Boot console, but if Axon is booted properly, you can access it using Type-C to USB, but I don’t think it will be useful for you.

https://docs.vicharak.in/vicharak_sbcs/axon/axon-os-configuration/vicharak-config/usb-tethering/

Even though it might not work, Have you tried to erase emmc first using ef command ?

can you share a few more details so we can pinpoint what went wrong?

  1. Which exact system image and kernel version are you using on the Axon board?
  2. What kind of ARM64 applications were you building natively using Docker?