Setup trusted Docker registry on a Raspberry Pi to host netPI containers - Printable Version +- Hilscher Community Forum (https://forum.hilscher.com) +-- Forum: netPI 3 - Docker featuring Industrial Raspberry Pi 3 platform (https://forum.hilscher.com/forum-1.html) +--- Forum: Software (https://forum.hilscher.com/forum-5.html) +--- Thread: Setup trusted Docker registry on a Raspberry Pi to host netPI containers (/thread-291.html) Pages:
1
2
|
Setup trusted Docker registry on a Raspberry Pi to host netPI containers - Armin@netPI - July-18th-2018 How to setup an own trusted Docker Registry Server (comes as a container from Docker Hub) to push and pull Docker images to and from. As example a standard Raspberry Pi (RPi) preloaded with Raspbian OS is used but you can be any Linux Host: Make a basic setup of your RPi:
https://youtu.be/0QRo3nAkUfo RE: Setup trusted Docker registry on a Raspberry Pi to host netPI containers - PhilippS - November-2nd-2018 Hi, i followed this setup using a netIoT not a netPi. Everything went fine until i uploaded the certificate with net Web-GuI. After the restart i cannot connect to the netIoT via Wifi or cable using the static ip port or the dhcp port i allways get a time out for the static ip and a not found error for the dhcp. RE: Setup trusted Docker registry on a Raspberry Pi to host netPI containers - Armin@netPI - November-2nd-2018 (November-2nd-2018, 10:04 AM)PhilippS Wrote: i followed this setup using a netIoT not a netPi You mean you bought a NIOT-E-TPI Edge Gateway instead of a netPI? Is my understanding correct? This one?: https://www.hilscher.com/products/product-groups/industrial-internet-industry-40/netiot-edge/niot-e-tpi51-en-reeis/?cats= RE: Setup trusted Docker registry on a Raspberry Pi to host netPI containers - PhilippS - November-2nd-2018 Yes. we are using this gateway: https://www.hilscher.com/products/product-groups/industrial-internet-industry-40/netiot-edge/niot-e-tijcx-gb-reeis/? the registry is running on standart raspberry pi. RE: Setup trusted Docker registry on a Raspberry Pi to host netPI containers - Armin@netPI - November-2nd-2018 Hello Philipp, ... but your problem is not the Raspberry registry - which is running fine as I have understood -, your problem is the NIOT-E-TIJCX-GB-RE is not running fine any more, correct? You said, you used the *.pem file and have imported it into your NIOT-E-TIJCX-GB-RE device and after you did that, the device was not responding any more and you cannot reach the Web GUI any more, correct? Or when did the problem started to occur? Thx Armin RE: Setup trusted Docker registry on a Raspberry Pi to host netPI containers - PhilippS - November-2nd-2018 Hi armin, yes I have the registry running on the Raspberry pi. Everything went fine until step 3 in Work on your netPI. I uploded the *.pem using the WebGUI and issued a reboot. After the reboot I could not reconnect to the Gateway. I connected directly to the Gateway using a cable. I tried both ports. I am not able to connect to the Gatway GUI anymore. If I try to connect via Port 1 using the dchp server I get a Webpage not found error in the browser. If I try to connect via Port 2 using a static IP connecting to the static IP of the Port I get a timeout. I tried pinging the device via powershell and got a timeout. RE: Setup trusted Docker registry on a Raspberry Pi to host netPI containers - Armin@netPI - November-2nd-2018 Ok Philipp, understood your problem. Basically it seems you did everything well. I couldn't do it better. The *.pem file should never cause the NIOT Edge Gateway causing a boot failure in my opinion. Since Edge Gateways are not supported through this forum but through Hilscher Hotline, please send your *.pem file and your inquiry to hotline@hilscher.com. They will take care of it. One thing in addition. The edge gateway your are using is a x86 intel process based device. All netPI Docker containers will not on this Edge Gateway machine. But I agree that a registry can run on any machine, also on a Raspberry, and host ARM based and x86 based container images. Thx Armin RE: Setup trusted Docker registry on a Raspberry Pi to host netPI containers - Armin@netPI - November-3rd-2018 By the way ... if the device is not responding any more as you describe ... the only way to recover it from this state is to reset it to factory default using a USB stick and the latest firmware from here https://www.hilscher.com/de/support/downloads/ on it RE: Setup trusted Docker registry on a Raspberry Pi to host netPI containers - rehaas - January-31st-2019 Hallo Armin, we have setup a registry wihin our company which is available by the hostname docker01 and it ist working from any Raspberry Pi. If we try to pull images from the Portainer Site on the NetPi we always get the same error: Failure Get https://docker01.local/v2/: dial tcp:lookup docker01.local: no such host I can ping the server from inside a Container on the NetPi, so I think the network settings on the NetPi are correct (DHCP). In the syslog i can see following lines. I guess the netpi uses the google dns server only <30>1 2019-01-31T10:12:56+00:00 NTB827EBEADCB9 dockerd 1463 - - time="2019-01-31T10:12:56.012225733Z" level=info msg="No non-localhost DNS nameservers are left in resolv.conf. Using default external servers: [nameserver 8.8.8.8 nameserver 8.8.4.4]" <30>1 2019-01-31T10:16:24+00:00 NTB827EBEADCB9 dockerd 1463 - - time="2019-01-31T10:16:24.722309664Z" level=info msg="No non-localhost DNS nameservers are left in resolv.conf. Using default external servers: [nameserver 8.8.8.8 nameserver 8.8.4.4]" Do you have any idea what is happening here. Best Regards Reinhold RE: Setup trusted Docker registry on a Raspberry Pi to host netPI containers - Armin@netPI - January-31st-2019 Which version of netPI do you use? Versions >= 1.1.4.0? So if yes, do you have defined your server as a registry right? The error indicates to me that the name "docker01.local" cannot be resolved by your DHCP server. How about using a registry with the name" docker01" without ".local" and if nothing else works just enter the plain ip address instead of "docker01.local" for test purposesy, then resolving names it not necessary at all. |