Container doesn't start, no logs, how can I debug the problem?

Hi, since yesterday I’ve tried all possible solutions, trying to install nodered/node-red:4.0.4-18-minimal, 20 and 22, and 3.1.22 supporting v6 processors amd many more, formatting each time before the usb stick with ext4, changing root path and so on.
The router has v7 processor so 4.04 should work, the image is downloaded and from disk monitoring sector written have right sizes (about 300MB for minimum, 700 for standard image), when it finished I can’t start it, it wrotes simply and just “stopped”, on logs I can see only get and downloaded lines, even if I’ve enabled containers and other logs on memory, I can’t see where it stops and what is going wrong. Mikrotik misses the chance to browse files, physically I can’t take out the stick and whats on a PC. How can I know deeper?

The same commands worked on CHR, the I can see it compared the /usr/src/node-red Work dir, on ac3 nothing about that, looks the installation script has not been executed. On CHR I used disk1, here I’m using USB1, can it be because of that?

for more infos I’ve reported on last posts here: http://forum.mikrotik.com/t/running-node-red-on-container-which-one/178801/18

As you read in topic I’ve managed to install NR manually, using an Alpine image. I don’t know if someone may be interested to understand why the NR image doesn’t install directly