Mikrotik CCR2004-1G-12S+2X's rom is too small, only 128M, but it has 4G RAM, so it has set ramdisk=1G, but the openwrt image in the container cannot run. After running, it is stopped immediately. What's the reason?

Do you have logging enabled? What does that say?

logging=yes

/system/device-mode/update container=yes
/disk add type=tmpfs tmpfs-max-size=1000M slot=RAM
/集装箱r/config/set registry-url=https://registry-1.docker.iotmpdir=RAM

/interface/veth/add name=veth1 address=172.17.0.2/16 gateway=172.17.0.1
/interface/bridge/add name=dockers
/ip/address/add address=172.17.0.1/16 interface=dockers
/interface/bridge/port add bridge=dockers interface=veth1
/ip/firewall/nat/add chain=srcnat action=masquerade src-address=172.17.0.0/16

/集装箱r/envs/add env_list=linux_envs key=PASSWD value="letmein"
/集装箱r/mounts/add name=linux_data src=RAM/docker/linux_data dst=/data

add remote-image=unifreq/openwrt-aarch64:latest interface=veth1 envlist=linux_envs root-dir=RAM/docker/linux_root mounts=linux_data hostname=openwrt

about logging file

getting layer sha256:a78819ced238e05f3cc7811c2f5c370be2125586cdf224ac204293083f7bc4da
layer sha256:a78819ced238e05f3cc7811c2f5c370be2125586cdf224ac204293083f7bc4da downloaded
import successful, container 2f370818-f547-404b-89b5-e65c453199b7

You can use armvirt target -

Still not, as before

docker importhttps://downloads.openwrt.org/snapshots ... tfs.tar.gzopenwrt-arm64
docker save openwrt-arm64 > openwrt_arm64.tar

I set "CMD" tothen connect to the console (or whatever # the container is) and poke around. For some containers, I figure out that there's a permissions problem, or some app is missing a library, or it can't find a file it's looking for.

I've tried it on the same exact setup and I, too, can't keep the container running. I'll have to test on another machine without a RAM disk and on 7.6.

Thanks, I managed to repeat this issue. This was broken somewhere from stable 7.6 to rc, release.
You can use 7.6 for now, as bare Openwrt uses only 8.8MB on arm64 systems

Thanks, I managed to repeat this issue. This was broken somewhere from stable 7.6 to rc, release.
You can use 7.6 for now, as bare Openwrt uses only 8.8MB on arm64 systems

So what exactly is broken? Use of the RAM disk for container storage?

So what exactly is broken? Use of the RAM disk for container storage?

In this case, cause is not related to tmpfs

Nice.

Downgraded my router to 7.6, then got the container working. Snapshot versions don't have a GUI, so this is what I ended up preparing for the router.
And with that, we have a GUI:

Downgraded from 7.7 to 7.6?

Nice.

Downgraded my router to 7.6, then got the container working. Snapshot versions don't have a GUI, so this is what I ended up preparing for the router.

Code:Select all

docker import https://downloads.openwrt.org/releases/22.03.2/targets/armvirt/64/openwrt-22.03.2-armvirt-64-default-rootfs.tar.gz openwrt-arm64 docker save openwrt-arm64 > openwrt_arm64.tar

And with that, we have a GUI:

Screenshot 2022-12-28 at 11.15.10 AM.png

Downgraded from 7.7 to 7.6?

Yeah. I had upgraded to 7.7 to try the RAM disk. Switched back to 7.6 and just used the NAND.

Nice.

Downgraded my router to 7.6, then got the container working. Snapshot versions don't have a GUI, so this is what I ended up preparing for the router.

Code:Select all

docker import https://downloads.openwrt.org/releases/22.03.2/targets/armvirt/64/openwrt-22.03.2-armvirt-64-default-rootfs.tar.gz openwrt-arm64 docker save openwrt-arm64 > openwrt_arm64.tar

And with that, we have a GUI:

Screenshot 2022-12-28 at 11.15.10 AM.png

Hello
Is it possible for you to fully explain the installation method? I did the settings according to the official Mikrotik videos on YouTube and followed your instructions on both 7.9 and 7.6 but still got the error that it wouldn't run.

----

update:

My router model is ax3 and it seems that none of the branches are working at the moment! (armvirt)