Hello
when I try to install a container, I get this error
error code getting container config: 400
error parsing container config
was unable to import, container 4c9aac65-8d50-4270-aae2-6430d6564f05

Some problem on my rb5009 7.17.2

i have the same problem Rb3011

Which registry url is set in containers config?

This is also happening to me on ROS 7.17.2 (error 400)

I even tried to download the image and import it myself using the instructions by the wiki and it’s failing to extract. (Stuck extracting forever)

Really wish we would get detailed logs on what’s happening. It’s hard to troubleshoot.

Also the registry I’m using is https://registry-1.docker.io/

You can add log topics debug,container and see if something more is logged related to this error.

This is also happening to me on ROS 7.17.2 (error 400)

I even tried to download the image and import it myself using the instructions by the wiki and it’s failing to extract. (Stuck extracting forever)

Really wish we would get detailed logs on what’s happening. It’s hard to troubleshoot.

Also the registry I’m using is https://registry-1.docker.io/

That Registry URL seems to be unavailable try https://registry.hub.docker.com/

Check with this, try to execute from Terminal: You should get: finished
Where url placeholders can be get from remote image format {namespace}/{repository}:{tag}, if {tag} is not specified latest is used.
For example for Pi-hole container namespace and repository are named pihole (pihole/pihole) and fetch url will be then: https://registry.hub.docker.com/v2/name ... ags/latest

Check with this, try to execute from Terminal:

Code: Select all

:put ([/tool/fetch url="https://registry.hub.docker.com/v2/namespaces/{namespace}/repositories/{repository}/tags/{tag}" output=user as-value]->"status")

You should get: finished
Where url placeholders can be get from remote image format {namespace}/{repository}:{tag}, if {tag} is not specified latest is used.
For example for Pi-hole container namespace and repository are named pihole (pihole/pihole) and fetch url will be then: https://registry.hub.docker.com/v2/name ... ags/latest

I ran the command with a few repos and those finish. My problem seems to be no matter which container I try, Technitium/dns-server, PiHole (from wiki example) and even a docker hello-world for the purposes of no mounts, env being needed. In the logs I always get the same error was

unable to import, container 2eb2e36f-23ef-4ea5-b780-70fb6f0c25ac

This also was using the old registry that I mentioned before, and also the new one https://registry.hub.docker.com that was suggested. After trying a few different times I will then get

"error code getting container config: 400"
"error parsing container config"
"was unable to import, container X"

Not sure if this has to do with updating ROS as I had no problem running a container before on v7.16. (I just saved my old /container/add line from when I first created the container and tried to run it again)

It seems new ROS version issue if for same containers fetch command is not failing, maybe it is building docker hub API url wrong. Container debug logs did not help? Maybe there is a debug log from which url is trying to fetch when building container.

Exactly the same error here and ROS 7.12.2, trying to install cloudflare tunnel container. Tried different registry url also as suggested, but no luck

Mauro

It seems new ROS version issue if for same containers fetch command is not failing, maybe it is building docker hub API url wrong. Container debug logs did not help? Maybe there is a debug log from which url is trying to fetch when building container.

Enabling logging on the container didn't provide any additional information sadly. I will upgrade to the ROS v7.18 beta and see if that makes a difference and report back.

Update - Upgrading to ROS v7.18 beta 5 fixed my problem ran the same command previously and now my container is running. I am no longer encountering the unable to import container. Looks like it's just a bug with ROS v7.17

Check with this, try to execute from Terminal:

Code: Select all

:put ([/tool/fetch url="https://registry.hub.docker.com/v2/namespaces/{namespace}/repositories/{repository}/tags/{tag}" output=user as-value]->"status")

You should get: finished
Where url placeholders can be get from remote image format {namespace}/{repository}:{tag}, if {tag} is not specified latest is used.
For example for Pi-hole container namespace and repository are named pihole (pihole/pihole) and fetch url will be then: https://registry.hub.docker.com/v2/name ... ags/latest

I ran the command with a few repos and those finish. My problem seems to be no matter which container I try, Technitium/dns-server, PiHole (from wiki example) and even a docker hello-world for the purposes of no mounts, env being needed. In the logs I always get the same error was

unable to import, container 2eb2e36f-23ef-4ea5-b780-70fb6f0c25ac

This also was using the old registry that I mentioned before, and also the new one https://registry.hub.docker.com that was suggested. After trying a few different times I will then get

"error code getting container config: 400"
"error parsing container config"
"was unable to import, container X"

Not sure if this has to do with updating ROS as I had no problem running a container before on v7.16. (I just saved my old /container/add line from when I first created the container and tried to run it again)

you using a tag when pulling your container? for example technitium/dns-server:latest

I ran the command with a few repos and those finish. My problem seems to be no matter which container I try, Technitium/dns-server, PiHole (from wiki example) and even a docker hello-world for the purposes of no mounts, env being needed. In the logs I always get the same error was




This also was using the old registry that I mentioned before, and also the new one https://registry.hub.docker.com that was suggested. After trying a few different times I will then get



Not sure if this has to do with updating ROS as I had no problem running a container before on v7.16. (I just saved my old /container/add line from when I first created the container and tried to run it again)

you using a tag when pulling your container? for example technitium/dns-server:latest

Yes I was, I tried technitium/dns-server:latest and even technitium/dns-server:latest@sha256:6f25ba81ad8be0019cb3d439d8452435614b40d2fe8252fced684eef277e2257 (I thought this might help as I seen in v7.18 there was a change about how containers choose the correct arch, didn't know if v7.17 was grabbing the wrong arch which caused it to fail importing)

For fetching latest tagged remote image is not mandatory to specify tag, it will be added by default, you can see when container is created that it has :latest tag even it is not specified. At least it is behaving like that up to 7.16, not tried on newer versions.

Update - Upgrading to ROS v7.18 beta 5 fixed my problem ran the same command previously and now my container is running. I am no longer encountering the unable to import container. Looks like it's just a bug with ROS v7.17

Man, love you, i was going crazy and it was all for a bug >_<

working flawlessly on 7.18

Thank you

It seems something is charged on Docker Hub API side, it no longer works also on ROS 7.16 which I'm using and probably on all lower versions than 7.18. Maybe because of Docker Hub API issues MT decided for 7.18 to switch default repository url to https://lscr.io which is not working on lower versions.
That is quite inconvenient for 16MB storage devices which cannot upgrade to 7.18 due to lack of free space on storage. Now only with manual upload of docker image is possible to add container... Very disappointing.

And then there is this Docker issue https://github.com/docker/cli/issues/5476 when trying to save image on different architecture from pulled image. Just great...

Also a possible bug, if you don't have a registry set (blank) after upgrading to 7.18 beta 5, it doesn't look like editing the registry via Winbox in container config will stick. I was able to confirm this by "/container/config print" as it still showed "assumed-registry-url: https://lscr.io" instead of the specific registry I put. Checking the container config (winbox, gui) after rebooting also showed that container config registry was empty.

After changing the registry via the terminal with the "/container/config set registry-url=" it look like it took and the registry was updated when running the "/container/config print" again. I was also able to confirm editing the registry via winbox gui was now working after at least setting it once via terminal.

Strange.

Update - Reported this issue to Mikrotik support@mikrotik.com. They were able to reproduce it and said it would be fixed on a later update.

Same problem on hAP ax^3 ROS 7.17.2
I have a working container that I installed in the previous version of ROS 7.16.x which starts and is fully functional, but I can't install new ones after updating to 7.17.2
Wouldn't experiment with 7.18 beta, taking into account that even the stable version is quite problematic.
Did anyone managed to solve this issue on 7.17.2?

This not related specifically to 7.17.x version, is seems it doesn't work on all versions <7.18 due to DockerHub API changes.

"error code getting container config: 400" , how to installing pihole container now?

You can pull and save image to file with Docker: https://docs.docker.com/reference/cli/d ... mage/save/, then upload saved image to ROS and create container from it by using file parameter, not remote-image. But here is a bug in Docker when saving image https://github.com/docker/cli/issues/5476 which I'm facing too (on macOS), I didn't try with other containers management applications, like Podman. Probably with Podman saving image will work.

Same problem on CCR2116-12G-4S+ ROS 7.17.2

Just to follow up regarding Docker image save bug https://github.com/docker/cli/issues/5476, using Podman works and saved image is successfully added as container in ROS. Tested on Linux, probably works same on other OS where Podman can run.
Since currently on ROS versions <7.18 only way to add container is from container image file, here are steps using Podman how to pull image from DockerHub and save container image:

1. Pull image with command in format:
   Code: Select all

   # podman pull --arch <architecture> docker.io/<namespace>/<repository>[:tag]
   

   depending on ROS architecture where container needs to be added, <architecture> can be: arm64 for ARM64, arm/v6 or arm/v7 for ARM (32bit), amd64 for x86_64
   example for Pihole (pihole/pihole) for ARM (32bit) ROS:
   
   Code: Select all

   # podman pull --arch arm/v7 docker.io/pihole/pihole

2. Save image with command in format:
   Code: Select all

   # podman save -o <image_name>.tar docker.io/<namespace>/<repository>[:tag]
   

   example for pulled image from 1st step:
   
   Code: Select all

   # podman save -o pihole.tar docker.io/pihole/pihole
   

After image is saved, it can be uploaded to ROS, for eg. using drag'n'drop to Files over Winbox. Note: do not upload large images into Files root on devices where RAM (tmpfs) is root fs, use mounted external storage or flash (if there is enough space there).
After image is uploaded to ROS, when adding container use File (CLI file parameter) with uploaded filename path as container source instead Remote Image (CLI remote-image) and that should successfully create container.

Thanks a lot, optio. This solved the issue.

Just to follow up regarding Docker image save bug

Many thanks for this info, I was just getting hit by this issue with container.