hAP ax3 uses internal flash to extract container: no space to extract layer

RouterOS Containers
1

Brand new hAP ax3 running 7.8
Following the container instruction to run PiHole in a container result in error.
https://help.mikrotik.com/docs/display/ROS/Container
Connected is a ext4 formated SanDisk Ultra Fit 16GB

/interface/bridge/add name=dockers
/ip/address/add address=192.168.136.1 interface=dockers
/interface/veth/add name=veth1 address=192.168.136.2/24 gateway=192.168.136.1
/interface/bridge/port/add bridge=dockers interface=veth1
/ip/firewall/nat/add chain=srcnat action=masquerade src-address=192.168.136.0/24
/container/envs/add name=pihole_envs key=TZ value=Europe/Berlin
/container/envs/add name=pihole_envs key=WEBPASSWORD value=password
/container/envs/add name=pihole_envs key=DNSMASQ_USER value=root
/container/mounts/add dst=/etc/pihole name=etc_pihole src=usb1-part1/etc
/container/mounts/add dst=/etc/dnsmasq.d name=dnsmasq_pihole src=usb1-part1/etc-dnsmasq.d
/container/config/set registry-url= https://registry-1.docker.io tmpdir=usb1-part1/pull
/container/add remote-image=pihole/pihole:latest interface=veth1 root-dir=usb1-part1/pihole mounts=dnsmasq_pihole,etc_pihole envlist=pihole_envs

While extracting you see inceasing disk usage of internal flash (128MB)

2

is root-dir also pointing to usb drive?

3

Hi,
In my case, it worked only with FS FAT32 on USB drive. With others, I had errors while extracting.
On FAT32 it works well and stable.

4

yes, container root-dir points to usb drive as well, or is there any other root-dir, which I could configure.
/container/add remote-image=pihole/pihole:latest interface=veth1 root-dir=usb1-part1/pihole mounts=dnsmasq_pihole,etc_pihole envlist=pihole_envs

5

Did you format the stick with routeros or elsewhere. I’ll try it with FAT32 as well.

/disk/print
Flags: B - BLOCK-DEVICE; M, F - FORMATTING; p - PARTITION
Columns: SLOT, MODEL, SERIAL, INTERFACE, SIZE, FREE, FS
#     SLOT        MODEL              SERIAL                          INTERFACE                    SIZE            FREE  FS  
0 B   usb1        SanDisk Ultra Fit  4C531123351120102372            USB 3.00 5000Mbps  15 552 479 232                      
1 BMp usb1-part1                     @1'048'576-11'275'337'728                          11 274 289 152  10 988 240 896  ext4
2 BMp usb1-part2                     @11'275'337'728-15'552'479'232                      4 277 141 504   4 126 154 752  ext4
6

Make sure in container config you specify where the image needs to be pulled and extracted.

e.g. from my setup:
/container config
set ram-high=200.0MiB registry-url=https://registry-1.docker.io /
tmpdir=usb1-part1/pull

7

Thanks, but as you could see in the config above I did.

8

Apologies, missed that part.

9

Hi,
I think I did it from the Mikrotik Web interface.

Here is how it looks after the container deployment:

/disk/print  
Flags: B - BLOCK-DEVICE; M, F - FORMATTING; p - PARTITION
Columns: SLOT, MODEL, SERIAL, INTERFACE, SIZE, FREE, FS
#     SLOT        MODEL          SERIAL                INTERFACE                     SIZE             FREE  FS  
0 B   usb1        SanDisk Ultra  4C530001140424109145  USB 3.00 5000Mbps  125 292 249 088                       
1 BMp usb1-part1                 @512-125'292'249'088                     125 292 248 576  123 602 440 192  ext4
10

Hello guys,

I have the exact same problem on my hap ax3. (usb2.0 drive, 32 Gb, fat32) Firmware 7.10 routerbord & upgrade.

Anyone any bright ideas?

Greetz: Patrick

ps: i tried something different, formated the usb-stick with ext4. Had a look at FILES during the installation of the container. Something goes wrong during extraction of the downloaded tar.gz. (made it up to 150 mb, then it stops.
ps2: changed a cidr notation (ip/address) It works now (only thing is: pihole GUI is very slow)

11

For me helped resolve the issue when I configured the container to use a layer directory located on the USB drive:

/container/config/print
layer-dir: /usb/layers
tmpdir: /usb/pull