RouterOS 7.13 - no space to extract layer [worked before in 7.xx]

RouterOS Containers
1

Hi
After the upgrade to ROS 7.13 i always get the “no space to extract layer” during the container extraction.
This has worked before.
I have noticed this because after the upgrade to RouterOS 7.13 i also wanted to upgrade my PiHole container.
Everything works as expected up until the extraction. Then i get the “no space to extract layer” error.
As far as I can see (if I leave the files window open in Winbox) is that RouterOS attempts to unzip it to the local storage and not to the USB drive.
Any ideas please?
Is this a known issue in 7.13? I do not really want to downgrade.

Disk config:

disk print
Flags: B - BLOCK-DEVICE; M - MOUNTED; p - PARTITION
Columns: SLOT, MODEL, SERIAL, INTERFACE, SIZE, FREE, FS
#     SLOT        MODEL                     SERIAL                INTERFACE                     SIZE             FREE  FS  
0 B   usb1        SanDisk SanDisk 3.2 Gen1  A2003852CB065A46      USB 3.20 5000Mbps  125 162 225 664                       
1 BMp usb1-part1                            @512-125'162'225'664                     125 162 225 152  124 108 500 992  ext4

Container config:

/container mounts
add dst=/etc/pihole name=etc_pihole src=/usb1-part1/etc
add dst=/etc/dnsmasq.d name=dnsmasq_pihole src=/usb1-part1/etc-dnsmasq.d
/container config
set ram-high=200.0MiB registry-url=https://registry.hub.docker.com/v2/ tmpdir=usb1-part1/pull
/container envs
add key=TZ name=pihole value=Europe/Bucharest
add key=WEBPASSWORD name=pihole value=password
add key=DNSMASQ_USER name=pihole value=root
2

Hi

Amazingly, i have found the problem.

disk print showed the “usb1-part1” as BMp (Block, Mounted, Partition). However, file print did not show the usb1-part1 as disk. So the container was actually extracted on the local disk.

What I had to do: eject the drive (system/disks), physically remove the drive from the device and added it back. Once I’ve added it the usb1-part1 appeared in the file list and container installation completed successfully.

So, this looks like a bug in ros 7.14. The partition appears to be mounted when in fact it is now.

Hope this helps others facing the same issue.