"Docker official image" - can't get installed

RouterOS Containers
1

I’ve been running caddy container for a while with the script to update it every 10 days.
After last update - I realized that container is not working.
Using official docker image https://hub.docker.com/_/caddy

Then i’ve realized, that pulling that container - i get error “error code getting container config: 400” in around 80% of the time, because every, like fifth time, when i try to pull image - it works.

Then I’ve tried redis image: https://hub.docker.com/_/redis
Same story, succeeds like every 5th time (did not calculate exactly) and fails with the same error as caddy image.
Screenshot 2025-01-04 182327.png
Screenshot 2025-01-04 182543.png
Sometimes i just get this error:
Screenshot 2025-01-04 183012.png
Adguard image for instance having no issues, so I assume - the problem persists only with docker official images, where there is no parent directory, but instead pulling caddy, for instance becomes this remote image “library/caddy” or “library/redis”

Using this repo:
https://registry-1.docker.io

bitnami/redis image, for instance works, but, i gues using official image would be better? I’d like to host caddy on my router as well

Running 7.17rc3
Please, do not propose to manually upload pulled images from PC, that is not an option.

2

Seems to be fixed in 7.17rc6

3

Same error here on 7.17.1, with an image that has been working for weeks (cloudflared 2025.1.1) and also now with cloudflared:2025.2.0, none will start with the same error message even thought the ARM64 image exists for my RB5009 :confused:

4

yes, same with 7.17.1, I spent all night to install homeassistant. I had to install docker desktop and then download and import image directly do mikrotik … and then I found out, that in Mikrotik docker is no support for USB stick … (zigbee)

5

Same on 7.17.2

6

I’ve been running 7.16.2 on my RB 3011 (arm32) for about two weeks or so, and have been able to pull the official pihole image from Docker Hub several times. But today I’m getting “error code getting container config: 400” no matter how many times I try. The image installs with no issues from a locally-exported tar file. I don’t think this is an issue with a specific v7 release, but maybe Docker Hub changed something that Mikrotik needs to take a look at?

7

Other wrote that changing the registry URL might help:
http://forum.mikrotik.com/t/v7-18beta-testing-is-released/181371/411

8

I just discovered the issue with pulling official Docker images today. Initially, I thought it was related to the upgrade of RouterOS version, so I tried downgrading to versions 7.15 and 7.12, but that didn’t solve the problem. I realized that there might be some changes in the Docker Hub network that caused this issue.

Ultimately, to get everything working again, I had to pull the images on a new VPS using Docker, then save them as tar files and upload them to RouterOS for import. This method worked successfully and saved my system, restoring its functionality!

9

@arainbow, excellent work. Thank you!

10

My setup already uses the second url since day 1.

11

Have the same problem in 7.12.2
Can’t ping docker.com or docker.io from mikrotik’s terminal

I’ve been using this url from the start

12

You will find that you can’t ping it from anywhere else, either. It’s a bogus test; their network admins have blocked ping. Try an HTTPS pull instead.

13

Did not know that. But good to know, as it makes ROS completely useless for many home automation use cases, as many times it involves USB hardware.

14

7.18 works better but I’m still having issues with HaProxy for some reasons:

[cont] error response getting manifests: 401
was unable to import, container 1bc08c1f-978c-4468-99f1-92134348ef6b

No matter which version, with or without sha256 digest.

15

Official image not installed:

/container/add remote-image=nginx:latest interface=veth1 root-dir=docker/nginx logging=yes

Result:

[cont] error response getting manifests: 401

But, example in docs work fine:

/container/add remote-image=pihole/pihole interface=veth3 root-dir=docker/pihole

I’m change official image and add ‘library/’ to name image and this work fine:

/container/add remote-image=library/nginx:latest interface=veth3 root-dir=docker/nginx logging=yes

Version Mikrotik% 7.18.2

2 Likes
16

Thanks @Clevelus, adding the "library/" for my postgres download worked on RB5009 running 7.18.2 (and v7.20rc2 which I tested in desperation before seeing your post)

1 Like
17

Hi arainbow, can you help me in doing this?

want to pull library/alpine:latest to a ROS 7.17.2 container.

but want to do it via a local .tar file. I have one but it says no image found when copying to ROS.

image

got the file via this cmd "docker save library/alpine:latest -o alpine.tar"