[SOLVED] Portainer does not start container

[Steres]

Hello,

I´m trying to start a container on Portainer, but I get the ERROR message "No such image: hilschernetpi/example : latest".
I followed the whole instructions on hub.docker.com, but it does not work.
Maybe their is an Internet problem?
I connected my netPI to a hotspot from my phone to get Internet access so I can pull images. How can I check if I have Internet access. I only can see that the netPI is connected.

Thanks in advance

[Armin@netPI]

Two things have been discussed very often:

1.) First of all make sure you set the system time correctly (manually or via NTP). Else time differences between netPI's system time and the DockerHub time prevents loading an image
2.) Pulling from Docker Hub goes across port 5000. If you are behind a firewall not allowing a pull across port 5000 then pulling an image will not work. I had this case already recognized by on of the netPI user. After he released the port 5000, everything worked fine
3.) make sure you have written the image you want to pull correctly: for example I don't know the image "hilschernetpi/example : latest" you are referring to as well. So for me "No such image" is correct in my eyes. I know an image "hilschernetpi/netpi-nodered-fieldbus" for example.

Thx
Armin

[shunterAC]

I have also ran into this issue (after setting the time, checking for port 5000 and copy/paste from the readme).

I was able to start the container only after I went to /portainer/#/images/ and pulled the image before attempting to create/start the container.

Is that correct, or should you be able to create a container without a local image? Is there a timeout issue with pulling the image when creating the container?

Thank you
Steve

[Armin@netPI]

Hi Steve,

pulling the image on a Raspberry Pi 3B CPU (on netPI then also) takes longer than on other CPUs. This is because of the bottleneck (serial interface) between the CPU and the SD card used as memory storage and the small cache the CPU owns. Also it depends on the traffic that is ongoing on Docker hub, if you pull an image from there. Then also it has influences if you have Containers actively running already and of course it depends on how big your image is. All those parameters influence the Container load time.

Additionally I have a remark that since firmware 1.1.2.0 we improved the load time by removing a permanent logging of internal Docker messages. Please verify that you have this firmware or higher actively running on your netPI.

If you want to get rid of depencencies from Docker Hub, I recommend to set up a local registry anyway. Then at least this timing is constant.

And if I would summarize my experience till today I would say that seeing this timeout is rare and that starting a container with implicit pull works in 95% of all cases. The timeout is not caused by Docker running on netPI by the way, but due to a Web-Browser <-> portainer.io timeout.