• 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Setup trusted Docker registry on a Raspberry Pi to host netPI containers
#1
Follow the steps to setup a trusted Docker image hosting registry on a standard Raspberry Pi:


  1. Login to your Pi with a terminal program such as Putty and make you root in the console with
    $ sudo -i
  2. Install Docker first (if not already installed)
    $ curl -sSL https://get.docker.com | sh
  3. Make your registry hosting Raspberry Pi unique in your (office) network (a Pi has a default Hostname: raspberrypi) and give it a reasonable Hostname like myregistry.
    Why is a unique Hostname necessary at all? A discrete Hostname is necessary since it is strongly recommended that trusted CA certificates identifiying a device as secure should not be issued for the device's IP address but for its Hostname instead. Below you will recognize that we need to create exactly such a CA certificate to let clients accept our server as secure once the certificate is made available to them.
  4. Change with an editor (nano) the current Hostname raspberrypi to myregistry in the two files.
    $ nano /etc/hosts (string behind the ip address 127.0.1.1)
    $ nano /etc/hostname

  5. (optional) If you want to make the Hostname public in a windows based office network you have to install two additional services
    $ apt-get install samba
    $ apt-get install winbind

    Additionally the wins service needs to be activated. Edit the following file in an editor
    $ nano /etc/nsswitch.conf
    In the line hosts: add the term wins and mdns4 to the existing terms files, dns, mdns4_minimal and others
  6. Reboot the Pi
    $ reboot now
  7. After the reboot generate new SSH keys pairs. First remove old ones.
    $ rm /etc/ssh/ssh_host_*
  8. Reconfigure SSH server.
    $ dpkg-reconfigure openssh-server
  9. Restart SSH server.
    $ service ssh restart
  10. Create a folder e.g.certs on your Pi and move to it. (This folder will be mapped into the Registry Server Container later and will contain its certificates).
    $ mkdir -p /certs && cd /certs
  11. Generate a new private key devdockerCA.key.
    $ openssl genrsa -out devdockerCA.key 2048
  12. Generate root CA certificate devdockerCA.pem.
    $ openssl req -x509 -new -nodes -key devdockerCA.key -days 10000 -out devdockerCA.pem -subj "/C=DE/ST=Hessen/L=Hattersheim/O=Hilscher/OU=Hilscher/CN=myownca/emailAddress=myownca@hilscher.com"
  13. Generate a new private key named domain.key file for the Registry Server.
    $ openssl genrsa -out domain.key 2048
  14. Create a new file req.conf ($ nano /certs/req.conf) necessary for a proper signing procedure. Copy the following content to it (tailored to your credentials, especially the most important CN that has to match your Pi Hostname):
    [ req ]
    distinguished_name = req_distinguished_name
    req_extensions = v3_req
    prompt = no
    [ req_distinguished_name ]
    C = DE
    ST = Hessen
    L = Hattersheim
    O = Hilscher
    OU = netIOT
    CN = myregistry
    emailAddress = mypi@hilscher.com
    [ v3_req ]
    keyUsage = keyEncipherment, dataEncipherment
    extendedKeyUsage = serverAuth
    subjectAltName = @alt_names
    [ req_ext ]
    subjectAltName = @alt_names
    [ alt_names ]
    DNS.1 = myregistry
    DNS.2 = myregistry.local
    DNS.3 = myregistry.domain
    IP.1 = 127.0.0.1

  15. Excecute certificate signing request.
    $ openssl req -new -key domain.key -out dev-docker-registry.com.csr -config req.conf
  16. Cross sign the server certificate with the CA root certificate and generate domain.crt file.
    $ openssl x509 -req -in dev-docker-registry.com.csr -CA devdockerCA.pem -CAkey devdockerCA.key -CAcreateserial -out domain.crt -days 10000 -extensions req_ext -extfile req.conf
  17. Let the root CA certificate become known on your Pi (else pushing to the Registry Server from the Pi itself (later topic) is not possible.
    $ cp /certs/devdockerCA.pem /usr/local/share/ca-certificates/devdockerCA.crt
    $ update-ca-certificates
    $ reboot now

  18. Start the registry on your Pi as a container and map the certs folder into it.
    $ docker run -d --restart=always --name registry -v /certs:/certs -e REGISTRY_HTTP_ADDR=0.0.0.0:443 -e REGISTRY_HTTP_TLS_CERTIFICATE=/certs/domain.crt -e REGISTRY_HTTP_TLS_KEY=/certs/domain.key -p 443:443 armbuild/registry:2
  19. Check if the Registry Server is running on your Pi by using its REST API reading the available repositories
    $ curl https://myregistry.local:443/v2/_catalog
    {"repositories":[]} -> returns empty list of repositories, which is fine.
  20. Pull a test image from Docker Hub onto your Pi
    $ docker pull hilschernetpi/netpi-debian-stretch:latest

  21. Tag the image with a name fitting to the name of your registry to prepare it for a push to it
    $ docker tag hilschernetpi/netpi-debian-stretch:latest  myregistry.local/mytest:latest

  22. Push the tagged image to your registry
    $ docker push myregistry.local/mytest:latest

Work to do on your netPI:

  1. Copy the previously created /certs/devdockerCA.pem file from your Pi to a location where it can be uploaded over netPI's Web-GUI. Typically you would use an FTP client such as WinSCP to copy it to your PC/machine running the web browser.
  2. Upload the pem file to your netPI using the Security/Public Key Infrastructure menu, highlighting then Trusted Certification Authorities and clicking upload finally as the picture shows:
       
  3. Reboot the netPI to let the new trusted CA certificate/authority become known on the system
  4. Finally pull the created test image from the registry onto your netPI. Use netPI's Docker Web-GUI and select Images in the left menu pane.
    Enter there the string mytest:latest as image name and as registry myregistry.local. Then click Pull the image. netPI will now pull the image from your private registry instead of Docker Hub.
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply
#2
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.
  Reply
#3
(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/produc...eeis/?cats=
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply
#4
Yes.

we are using this gateway: https://www.hilscher.com/products/produc...-gb-reeis/?

the registry is running on standart raspberry pi.
  Reply
#5
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
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply
#6
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.
  Reply
#7
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
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply
#8
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
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply
#9
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
  Reply
#10
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.
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  CODESYS - Control for Raspberry Florian 1 5 1 hour ago
Last Post: Armin@netPI
  [INFO]Docker DNS server Armin@netPI 0 10 March-7th-2019, 09:02 AM
Last Post: Armin@netPI
  [SOLVED] node-red Dashboard Docker Image for netPI? anrodriguez 1 18 February-7th-2019, 05:35 PM
Last Post: Armin@netPI
Information netPI Docker REST API for versions >= V1.1.4.0 Patrick@netPI 0 28 January-29th-2019, 01:40 PM
Last Post: Patrick@netPI
  [SOLVED] Keep getting a message that session expired in Docker SteveO 2 41 January-24th-2019, 11:50 AM
Last Post: Armin@netPI
  [SOLVED] Running Eclipse inside Docker Rahulsagar 6 50 January-21st-2019, 04:03 PM
Last Post: Rahulsagar
  [INFO] Best base image to use for own containers Armin@netPI 1 110 January-15th-2019, 08:58 PM
Last Post: Armin@netPI
  [SOLVED] Authenticate against Docker Registry PBulach 19 610 September-19th-2018, 12:31 PM
Last Post: Armin@netPI
Information Managing netPI's Docker from remote via RESTful API for netPI versions < 1.1.4.0 Armin@netPI 4 275 September-7th-2018, 10:41 AM
Last Post: Armin@netPI
  Docker push SebastianSoller 2 178 August-22nd-2018, 08:26 PM
Last Post: Armin@netPI

Forum Jump:


Users browsing this thread: 1 Guest(s)