import adguard dns container image problem

soran1 · Sat Feb 18, 2023 7:41 pm

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)其just not there any more so ,what to use for the registry URL

Zakazulu · Sun Feb 19, 2023 3:51 pm

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?

soran1 · Mon Feb 20, 2023 1:41 am

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

tricyclevent · Mon Feb 20, 2023 3:19 pm

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..

Z0ltan · Mon Feb 20, 2023 10:19 pm

It seems docker now requires authentication, however that’s only supported in 7.8.

tricyclevent · Tue Feb 21, 2023 12:03 pm

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).

Z0ltan · Tue Feb 21, 2023 8:50 pm

Can you try withhttps://index.docker.io/v2/? And use your working docker credentials.

tricyclevent · Wed Feb 22, 2023 8:20 pm

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?

tricyclevent · Wed Feb 22, 2023 9:48 pm

404:

viewtopic.php?t=192810#p981824

viewtopic.php?p=985969#p985966
thx CTassisF

Z0ltan · Thu Feb 23, 2023 3:10 pm

有趣,谢谢这些链接。在第一个vestigation 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.

Fri Feb 24, 2023 8:58 am

thanks for reporting this, we will check how to fix this in upcoming versions

Amm0 · Fri Feb 24, 2023 12:18 pm

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.

blackhandnz · Tue Feb 28, 2023 9:31 pm

Anyone get this to work in v7.8, I still get the same issue (I assume its not fixed yet?)

Zakazulu · Tue Feb 28, 2023 10:10 pm

I got it working using a build earlier than latest. Try; adguard/adguardhome:v0.108.0-b.25

blackhandnz · Tue Feb 28, 2023 10:40 pm

I got it working using a build earlier than latest. Try; adguard/adguardhome:v0.108.0-b.25

Thanks that worked

Rhoos · Wed Mar 01, 2023 4:21 pm

I got it working using a build earlier than latest. Try; adguard/adguardhome:v0.108.0-b.25

Thanks, it worked for me!

blackhandnz · Wed Mar 15, 2023 9:22 pm

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

antoxic · Mon Mar 20, 2023 11:41 am

Did somebody managed to run the latest version without downloading the file to pc first?

Amm0 · Mon Mar 20, 2023 12:06 pm

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.

antoxic · Mon Mar 20, 2023 12:31 pm

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!

antoxic · Mon Mar 20, 2023 12:50 pm

While the import issue is getting resolved, to update to the latest version of the container you can do this.
...

Thanks. Manual download and run worked for me as well!

Tue Mar 21, 2023 9:20 am

Thanks! Well, I hope that a new release is coming soon, at least as a beta!

Fix is included in upcoming beta

Z0ltan · Sun Mar 26, 2023 11:35 am

Anyone confirmed if it’s working?

*) container - improved "container pull" to support OCI manifest format;

tricyclevent · Sun Mar 26, 2023 8:31 pm

7.9beta4

Adguard:Adguard

error response getting manifests: 401
was unable to import, container

Z0ltan · Mon Mar 27, 2023 3:26 pm

It's actually adguard:adguardhome can you please try with that as well?

tricyclevent · Mon Mar 27, 2023 6:56 pm

adguard:adguardhome
importing remote image: adguard, tag: adguardhome
error response getting manifests: 401
was unable to import, container bdd79662-4b0f-46ca-9deb-24d5890d6891

adguard/adguardhome
importing remote image: adguard/adguardhome, tag: latest
was unable to import, container c3a3d65f-612f-421b-83df-8b30dc724ad3

no 401 message.

optio · Mon Mar 27, 2023 8:03 pm

adguard:adguardhome
importing remote image: adguard, tag: adguardhome
error response getting manifests: 401
was unable to import, container bdd79662-4b0f-46ca-9deb-24d5890d6891

There is noadguardhometag for that image, see:https://hub.docker.com/r/adguard/adguardhome/tags
Syntax is: [:], if tag is not specified it useslatestif exists

adguard/adguardhome
importing remote image: adguard/adguardhome, tag: latest
was unable to import, container c3a3d65f-612f-421b-83df-8b30dc724ad3

no 401 message.

Could be related to ROS docker image compatibility (OCI manifest format), try this solution:viewtopic.php?t=193727#p985424

Z0ltan · Mon Mar 27, 2023 10:37 pm

Sorry for the wrong syntax, it should be adguard/adguardhome:latest

No 401 seems promising but looks like still not working, thanks for checking, maybe the team will fix it by 7.9 final.

Z0ltan · Mon Apr 03, 2023 3:30 pm

Can you check if it works with 7.9rc1?

jodansi90 · Tue Apr 04, 2023 6:46 am

Can you check if it works with 7.9rc1?

It doesn't work!

Z0ltan · Tue Apr 04, 2023 4:42 pm

Interesting, I spun up 7.9rc1 as a virtual machine and found this in the logs:

13:39:58容器,信息,调试远程ima进口ge: adguard/adguardhome, tag: latest
13:39:58 system,info item added by admin
13:40:00 container,info,debug was unable to import, container 69aeeb3b-32d0-4012-8943-32344d748243
13:40:11 container,info,debug removing files, container 69aeeb3b-32d0-4012-8943-32344d748243
13:40:11 system,info item removed by admin
13:40:42 container,info,debug importing remote image: adguard/adguardhome, tag: latest
13:40:42 system,info item added by admin
13:40:44 container,info,debug was unable to import, container d114a626-8a0f-4e26-a9f1-3d296b2bcc48

It seems it can download the image but cannot import it.

jodansi90 · Wed Apr 05, 2023 5:38 pm

Thanks! Well, I hope that a new release is coming soon, at least as a beta!

Fix is included in upcoming beta

It still doesn't work in Release 7.9rc1, help!

Josephny · Tue Apr 11, 2023 6:03 pm

Has this been fixed?

In the meantime, can anyone explain how I can download the Adguard container file on my Windows PC for moving to the RB5009?

import adguard dns container image problem Topic is solved

import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problemTopic is solved

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Re: import adguard dns container image problem

Who is online