I would like to know if the Raspi 3 + netHat behave like the netPI when it comes to develop docker app.
I bought the netHat, with the goal of using it as my dev. environment, and keep the netPI as my "production" platform, so I can test and develop into the Raspi and then upload the docker containers directly into the NetPi.

Is there any kind of differences into using both? I understood the netPi is locked and secured into the host part, so no docker CLI access / SSH... but what about the hardware / drivers / access to NetX51? is it the same?

I'm waiting to receive both this week, so I want to be sure that I made the right choice buying them.
thanks.
Vincent

We found another nice paper on the internet, where Roberto Morabito from company Ericsson examined the Docker performance compared to a native system on a Raspberry Pi 2. He presented his results on 2016 IEEE Conference on Computer Communications Workshops.

His summary is: "Results show an almost negligible impact of the container virtualization layer in terms of performance, if compared to native execution".

Find his paper officially published here on the IEEE.org. Tip: if you have no account, you find his paper published on many other platforms as well where you can download the document right away.

[EDIT] Performance Document appended to this post. Also nice to read: https://hackernoon.com/another-reason-wh...7207dec27f

Attached Files

  1603.02955.pdf (Size: 901.76 KB / Downloads: 1)

By default netPI listens to the following ports:

TCP:

• Port 80,nginx -> web server / reverse proxy
  
• Port 443,nginx -> web server / reverse proxy
  
• Port 49152, upnpd -> UPnP daemon
  

• 123,ntpd -> Network Time Protocol daemon
  
• 137,nbnsd -> Netbios Name Service
  
• 1900, upnpd -> UPnP daemon
  
• 5353, avahi-daemon -> Zeroconf
  
• 60843, avahi-daemon -> Zeroconf temporary port
  
• 36517, avahi-daemon -> Zeroconf temporary port
  
• 41429, dnsmasq -> DNS proxy temporary port
  

NPIX modules tailored to your requirements - in which your ideas can add to the basic functions of netPI - is a service we offer.

What you need are three things:

•    A PCBA
  
•    A metal bracket
  
•    Two screws
  

•    You share your idea with us. We make the design and take care of the whole production on a bid basis.
  
•    You take care of the design. You deal with the metal bracket manufacturer. You do the production yourself.
  
  

One of the first things you need to do, once a virgin NetPI3 got unboxed, is to setup NTP, according to the "netPI - Getting Started with the netPI" video. Otherwise, customers run into severe issues, such as not being able to run Docker containers. The reason for the need of NTP is obvious, but I wonder why doesn't the NetPI3 either:
- Setup a generic NTP by default, or
- Offer this setup in a kind of wizard, e.g. right after changing the password?
Is this an oversight? Are there any technical issues I don't grasp? Or is it planned, but you didn't yet had time to implement it?

Initially, when I connected my new NetPI3 to my LAN, I wasn't able to access it by the described instructions (opening the browser and enter the "name" mentioned on the sticker). I also couldn't "ping" it because the "name" could not be resolved.

After some debugging, I could resolve the issue by reconfiguring my router (pfsense): The DHCP-Server didn't automatically update the DNS entries. I can't remember the very details, because already some days past since then, but may claim is: I think that the way to initially access the NetPI3 is not working under all circumstances (possibly including some "pretty popular" ones, as my "pfsense" setup was quite virgin).

Question: Are you aware of that? If not, would it help if I reproduce the issue and provide more information on this?

Another possibly related question: In one of the forum posts you mention the Tcp/Udp ports opened by the NetPI3. According to that post, bonjour is running as well. Why? Can it be used as another option to initially access the NetPI3?

I'd like to keep up with new information. Therefore, I'd like to get notified by emails upon new forum entries. Either for each post and reply or just upon new posts or maybe as a daily summary (most preferred option). I couldn't find a way to setup this right now. Am I missing something? If not: Are you planning to implement such a feature?

Thanks for the new system software. Installation worked like a charm.

Just today, I was looking for a new software, but did not look at the forum. Instead, I checked out https://www.netiot.com/netpi/industrial-...-on-netpi/. Over there, I clicked the "download"-link - but that link is broken (404). That made me think that no "public" software was yet released. Maybe it'd be good to fix the link.

Hello all, looking for a little advice, all I want is a RaspberryPi (with Codesys) container that I can set (and change afterwards) its IP address. What network option do I need when creating the container (Bridge, host, Container).

netPI pulls images from trusted Docker registry servers only. Trusted servers provide a trusted certificate from an official Certificate Authority (CA) to rely on its digital signature. The most popular trusted Docker registry is Docker hub. But you can run trusted Docker registry servers yourself on-premise as well. We show you how.

Here is how you set up your own trusted Docker registry server with help of an official Certificate Authority such as Let's Encypt.

• First you need a domain name (hostname) of your server. Get one from noip for example. Let's suppose you got a name mydockerregistry.ddns.net.
  
• As next configure DynDNS service on your Internet Router as described here so that your router is reachable through your domain name over the internet.
  
• Then set up a physical server. Run Linux on it for quick results. Ubuntu will do it.
  
• Configure your Internet Router to forward the TCP ports 80 and 443 to the server. Port 80 is needed to demonstrate control over the domain during one time certification process. Port 443 is needed to run the Docker registry across.
  
• For an automated certificate issuance you need a web server installed on your server. For quick results we recommend Nginx. To install it simply call sudo apt-get install nginx.
  
• Additionally install CertBot, a software that is automatically requesting a certificate from Let's encrypt for your domain. On the web site select as software Nginx and as system Ubuntu and it will be providing you an installation instruction. Execute the proposed commands on your server.
  
• During the procedure you will be asked for the domain name you want the certificate for. Enter your domain name mydockerregistry.ddns.net(our example) at this stage.
  
• The certificates and keys will be genrated and stored on your server in the folder /etc/letsencrypt/live/mydockerregistry.ddns.net/. Port 80 forwarding on your Internet Router is no longer needed.
  
• Now install Docker on your server as described here
  
• The certificates and keys need a renaming and a merge so that the Docker registry can use them. Call
  cd /etc/letsencrypt/live/mydockerregistry.ddns.net/cp privkey.pem domain.keycat cert.pem chain.pem > domain.crtchmod 777 domain.crtchmod 777 domain.key
  
• Finally run the Docker registry with the following docker command
  $ docker run -d \  --restart=always --name registry \  -v /etc/letsencrypt/live/mydockerregistry.ddns.net:/certs \  -v /opt/docker-registry:/var/lib/registry \  -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 \  registry:2
  
• Now you are able to acess your Docker registry over mydockerregistry.ddns.net. e.g. call the command docker pull mydockerregistry.ddns.net/myimage for example to pull an image named myimage across the internet.