hello everyone,i have problem when i want to install or pull the docker image the problem is (error response getting manifests: 404)
when using( https://registry-1.docker.io) its just not there any more so ,what to use for the registry URL
i’m trying to set adguard on my rb5009 and i am getting the same error. On my AX3 i did the same thing and it just works?
i just find the sloution i had to download the adgaurd image file with windows docker and i save it as tar file then upload it to my 4011rb and its worked
I have the same problem. No more Adguard container possible for RB4011.
“error response getting manifests: 404”
“was unable to import, container 150b8c16-e633-4ade-9f88-61dc463961c5”
Can you upload the image? I have no idea how docker for windows works..
It seems docker now requires authentication, however that’s only supported in 7.8.
How to use the authentication?
In terminal i set up username & password. But how to connect?
I changed the url to: https://registry-1.docker.io/v2/
Tests all possibilities (urls, different dockers), but no success.
I m on 7.8rc2 (testing).
Can you try with https://index.docker.io/v2/ ? And use your working docker credentials.
Adguard/Adguardhome:
with Url: https://index.docker.io/v2/
i get: “error response getting manifests: 401”
with Url: https://index.docker.io/
i get: “error response getting manifests: 404”
Pihole/Pihole:
with Url: https://index.docker.io/v2/
i get: “error response getting manifests: 401”
with Url: https://index.docker.io/
Succes, download start, pihole starts with success
whats the difference on Adguard?
And are my credentials activ? How to check?
404:
http://forum.mikrotik.com/t/v7-8beta-testing-is-released/163742/1
http://forum.mikrotik.com/t/v7-8rc-is-released/164314/119
thx CTassisF
Interesting, thanks for those links. Upon first investigation I noticed Mikrotik was using a different registry than my docker installation on Synology and using that repo required authentication, that’s why I thought lack of authentication is the crux of the problem; I never thought the manifest format was changed. I guess we’re left with the manual export of the tar file from a system that’s actually capable of retrieving the container.
thanks for reporting this, we will check how to fix this in upcoming versions
Hmm. I recently trying to use ghcr,io as the “Container Registry” to pull /containers (e.g. /container/config/registry-url=https://ghcr.io) with GitHub’s CI for my own images.
Ran into this problem when building an image through GitHub’s Actions however…
But I bet it be similar with the adguard image too.
GitHub’s CI builder, by default uses “attestations” (metadata) and adds theses to the docker buildx:
docker buildx build --sbom=true --provenance=true ...
However, those options cause “fake platform” of “unknown/unknown” in the package (that must store them I guess) for download in the registry (e.g. GitHub’s DockerHub).
And RouterOS gets the same 404 and “error” status as reported for adguard.
Removing those explicitly disabling in the GitHub workflow.yaml “build-and-push-docker-images” action fixed my custom package:
# ...
- name: Build and push
uses: docker/build-push-action@v4
with:
context: .
push: true
sbom: false
provenance: false
platforms: linux/arm64,linux/arm/v7
But that’s not so easily done for other people’s packages. But default are “true” for both “sbom” and “provenance”, and that breaks RouterOS’s /container pull it seems… so that effect most public images built on GitHub I’d imagine.
This never would happen when using “docker save” locally, since the tar file doesn’t support Docker’s attestation AFAIK.
Anyone get this to work in v7.8, I still get the same issue (I assume its not fixed yet?)
I got it working using a build earlier than latest. Try; adguard/adguardhome:v0.108.0-b.25
Thanks that worked 
Thanks, it worked for me!
While the import issue is getting resolved, to update to the latest version of the container you can do this.
From your computer :
1.) docker pull adguard/adguardhome:latest@sha256:aa84b1ff0b5710052bdb8e63b4528dc9b634780019a125d3d4de320868b6cbf2
(where the digest corresponds to your Mikrotik’s architecture e.g. ARM64)
2.) docker save adguard/adguardhome > adguardhome.tar
3.) Upload to your RouterOS Device and use the uploaded file to create the container
Did somebody managed to run the latest version without downloading the file to pc first?
There is a bug in RouterOS that prevent a pull’ed image built using a newer metadata format from loading. So until Mikrotik fixes the bug, no. It’s not just adguard affected by this bug, so imagine a fix will come in the next release.
The tar file don’t contain any metadata so it avoid the bug, but you can only get those using the desktop clients.
Thanks! Well, I hope that a new release is coming soon, at least as a beta!