Container and RouterOS v7.18 [stable]

RouterOS Containers
1

Hello everyone!

I’m writing this post to discuss the changes introduced in RouterOS 7.18.
From the changelog, I see that the default registry URL has now been set to https://lscr.io.

I wanted to ask: Are there any difficulties using https://registry-1.docker.io as the registry?

I ask this because, recently, I have seen several posts here on the forum related to issues with pulling images from Docker Hub.

I have a CHR running RouterOS 7.18beta6, and I can only pull certain containers.
After running multiple tests to investigate the issue in depth, I noticed that I am unable to pull images that have the format :

For example, I can successfully pull:
zerotier (zerotier/zerotier:latest | Docker Hub)
cloudflared (cloudflare/cloudflared:latest | Docker Hub)

However, I cannot pull:
alpine (alpine:latest | Docker Hub)

In general, it seems that I can successfully pull images that follow the format:
/:

While I cannot pull images using the format:
:

Are there any known solutions to this issue?

Thanks!

2

library/alpine:latest

3

Perfect, thank you very much!
By using the format:
library/:
I am able to pull all containers successfully.

Do you know if there are any issues or limitations with the Docker Hub registry, considering that a different registry has been set as the default?

4

https://www.docker.com/blog/revisiting-docker-hub-policies-prioritizing-developer-experience/