NIOT-E-NPI3-EN

[Envisia-BR]

        Hello,
 
I am trying to upload a container on NodeRed NetPI without fieldbus, but I am unsuccessful. I would like to understand why? Container caught in Docker-hub as follows:
 
Best Regards..

[Armin@netPI]

I am sorry I cannot see your screen shot. Please edit your post, append the picture and choose option to embed the picture into post.

Thx
Armin

[Armin@netPI]

Well,

I still see two screen shots of Docker Hub web page. They look same to me. But I suppose this is not what you want to show. My expectation was that you post a screen shot with an error or any fault indication. But with this screen shot I cannot help.

Thx
Armin

[Armin@netPI]

I could highlight some videos for you showing how to get started with netPI:

https://www.youtube.com/watch?v=CB6bYfMbFhA

https://www.youtube.com/watch?v=A-asfhl7b0c

Maybe this is what you are searching for.

[Envisia-BR]

Well,

I still see two screen shots of Docker Hub web page.  They look same to me. But I suppose this is not what you want to show. My expectation was that you post a screen shot with an error or any fault indication. But with this screen shot I cannot help.

Thx
Armin

Hello Armin,


I am using a NETPI CORE model: NIOT-E-NPI3-EN.

I am trying to deploy Node-red Container from Docker-Hub: https://hub.docker.com/r/hilschernetpi/netpi-nodered

I did the configuration in Portainer.IO according to the tutorial, however when I start deploy I get this error message (image attached).

[Armin@netPI]

I have another proposal and I just want to see if netPI is able to pull the image of this container in general.

Your screen shot shows you are using the "container" tab in the left menu. Do you see the "Images" tab too?

Please use the "Images" tab and then insert the same string "hilschernetpi/netpi-nodered" just to pull the image. It will just pull the image and will not start a container. Then the image is stored locally first.

With this test I just want to see if there is a contact to the Internet with your netPI.

Thx
Armin

[Armin@netPI]

In addition to my remark please read this thread https://forum.hilscher.com/Thread-SOLVED...ing-deploy

Make sure your office firewall allows accesses to remote port 5000. This is where Docker service pulls the image from Docker Hub web site.

Do you have an original Raspberry Pi running in your office network to? If so you could easy check using the command "docker pull hilschernetpi/netpi-nodered" ... just to check internet connectivity to Docker hub web platform

Thx
Armin

[Envisia-BR]

In addition to my remark please read this thread https://forum.hilscher.com/Thread-SOLVED...ing-deploy

Make sure your office firewall allows accesses to remote port 5000. This is where Docker service pulls the image from Docker Hub web site.

Do you have an original Raspberry Pi running in your office network to? If so you could easy check using the command "docker pull hilschernetpi/netpi-nodered" ... just to check internet connectivity to Docker hub web platform

Thx
Armin

Armin,

I released port 5000 on my local router and still remain unsuccessful while uploading the container.

I did the test you requested, trying to download only the image, and I get this error message:

[Armin@netPI]

Well the error "connect: network is unreachable" seems to me still that netPI is not able not able to reach the web site "https://registry-1.docker.io/v2/".

But let me ask you this: In order to resolve the name "https://registry-1.docker.io/v2/" a DNS server setting with your router is needed that transforms the name "registry-1.docker.io" into an ip address which is "54.210.105.17" right now.

If you go into the network LAN settings dialog of your netPI ... which entry do you see in the line DNS? If there is non then netPI Linux cannot resolve the name to IP address.

Also what you can also check in principle is to call the "https://registry-1.docker.io/v2/" in your web browser under Windows for example and see if you browser is coming back with any response from Docker Hub platform.

Thx
Armin