Hello
when I try to install a contenair, I get this error
error code getting container config: 400
error parsing container config
was unable to import, container 4c9aac65-8d50-4270-aae2-6430d6564f05
Re: Unable to install contenairs
Some problem on my rb5009 7.17.2
Re: Unable to install contenairs
i have the same problem Rb3011
Re: Unable to install contenairs
Which registry url is set in containers config?
-
-
TrevinLC1997
just joined
- Posts: 13
- Joined:
Re: Unable to install contenairs
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/
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/
Re: Unable to install contenairs
You can add log topics debug,container and see if something more is logged related to this error.
Re: Unable to install contenairs
That Registry URL seems to be unavailable try https://registry.hub.docker.com/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/
Re: Unable to install contenairs
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
Code: Select all
:put ([/tool/fetch url="https://registry.hub.docker.com/v2/namespaces/{namespace}/repositories/{repository}/tags/{tag}" output=user as-value]->"status")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
-
-
TrevinLC1997
just joined
- Posts: 13
- Joined:
Re: Unable to install contenairs
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 wasCheck with this, try to execute from Terminal:You should get: finishedCode: Select all:put ([/tool/fetch url="https://registry.hub.docker.com/v2/namespaces/{namespace}/repositories/{repository}/tags/{tag}" output=user as-value]->"status")
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
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
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)"error code getting container config: 400"
"error parsing container config"
"was unable to import, container X"
Re: Unable to install contenairs
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.
Re: Unable to install contenairs
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
Mauro
-
-
TrevinLC1997
just joined
- Posts: 13
- Joined:
Re: Unable to install contenairs
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.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.
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
Re: Unable to install contenairs
you using a tag when pulling your container? for example technitium/dns-server:latestI 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 wasCheck with this, try to execute from Terminal:You should get: finishedCode: Select all:put ([/tool/fetch url="https://registry.hub.docker.com/v2/namespaces/{namespace}/repositories/{repository}/tags/{tag}" output=user as-value]->"status")
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
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
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)"error code getting container config: 400"
"error parsing container config"
"was unable to import, container X"
-
-
TrevinLC1997
just joined
- Posts: 13
- Joined:
Re: Unable to install contenairs
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)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)
Re: Unable to install contenairs
For fetching latest tagged remote image is not mandatory to specify it, 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.