Hello,

following instructions from:

https://help.mikrotik.com/docs/spaces/R ... /Container

i'm trying to run pihole on RB5009 (RouterOS 7.18.2).

After getting to the step of adding a container:

/container/add remote-image=pihole/pihole:latest interface=veth-pihole root-dir=usb1/containers/pihole mounts=dnsmasq_pihole,etc_pihole envlist=pihole_envs

i get error:

[cont] not ok registry auth response: 403 when adding a container

I've tried to set a login and password in containers config but without succes. Any ideas what could by the cause of the problem? All the setting are set like in in the example (except for the path - usbdisk1).

do you found a solution?

You should double-check that you've set the correct registry-url in your container config. For pulling from Docker Hub (which hosts pihole/pihole), it should be:

/container/config/set registry-url=https://registry-1.docker.io

If you're still getting the same error after confirming that, it's a good idea to open a support ticket :
https://mikrotik.com/support

registry.hub.docker.com/pi.....

Try this

do you found a solution?

A workaround only - installing the container from file, but it's no solution to the problem.

You should double-check that you've set the correct registry-url in your container config. For pulling from Docker Hub (which hosts pihole/pihole), it should be:

/container/config/set registry-url=https://registry-1.docker.io

If you're still getting the same error after confirming that, it's a good idea to open a support ticket :
https://mikrotik.com/support

the url is set properly: https://registry-1.docker.io

Same problem. Tried both URL's and neither work. Same error. These problems have been off and on since v7.9 seems to be very problematic.

If anyone has any other solutions, please advise.

If you’re getting this error, try adding the registry you’re using in the beginning of the remote-image field. So for me, cloudflare/cloudflared:latest was not working. It started working when I changed it to “registry-1.docker.io/cloudflare/cloudflared:latest”

I’m assuming this has to do with these two recent change notes from 7.18:

*) container - add default registry-url=https://lscr.io;
*) container - allow HTTP redirects when accessing container registry;
*) container - allow specifying registry using remote-image property;

If you’re getting this error, try adding the registry you’re using in the beginning of the remote-image field. So for me, cloudflare/cloudflared:latest was not working. It started working when I changed it to “registry-1.docker.io/cloudflare/cloudflared:latest”

I’m assuming this has to do with these two recent change notes from 7.18:

*) container - add default registry-url=https://lscr.io;
*) container - allow HTTP redirects when accessing container registry;
*) container - allow specifying registry using remote-image property;

Bingo.