Thanks. Manual download and run worked for me as well!
Fix is included in upcoming beta
Anyone confirmed if it’s working?
*) container - improved “container pull” to support OCI manifest format;
7.9beta4
Adguard:Adguard
error response getting manifests: 401
was unable to import, container
There isn’t a colon between them, but think it may have to be “fully qualified”.
I don’t use it, but this seems to work “adguard/adguard:latest” to extract now. IDK but maybe the tag is always required and it doesn’t assume latest.
It’s actually adguard:adguardhome can you please try with that as well?
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.
There is no adguardhome tag for that image, see: https://hub.docker.com/r/adguard/adguardhome/tags
Syntax is: <repo_image_path>[:], if tag is not specified it uses latest if exists
Could be related to ROS docker image compatibility (OCI manifest format), try this solution: http://forum.mikrotik.com/t/import-adguard-dns-container-image-problem/164536/1
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.
Can you check if it works with 7.9rc1?
It doesn’t work!
Interesting, I spun up 7.9rc1 as a virtual machine and found this in the logs:
13:39:58 container,info,debug importing remote image: 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.
It still doesn’t work in Release 7.9rc1, help!
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?
Hello, fix hopefully will come with next beta release.
Dear antonsb,
do you know when it could be (next beta release?)?
BR
Kamil
Hello, fix hopefully will come with next beta release.
beta will be released immediately after stable release. Probably next week.
beta will be released immediately after stable release. Probably next week.
you mean 7.10 beta?
Yes fixes will come with 7.10 branch - otherwise it will slow down existing 7.9 development.
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
Thanks, this worked for me ![]()