December-15th-2018, 08:14 AM
(This post was last modified: October-28th-2019, 05:19 PM by Armin@netPI.)
Dear Rahulsagar,
the story about netPI is special ... we tell customer indeed to collect experience with Docker and building own containers and starting/testing the software on a standard Rpi3 (at $30cost) and then if all the software has been passed the tests to buy a professional netPI afterwards which is a Docker Host only to run the software securely and not a development platform. So it is a fair offer to have a standard Rpi3 as development platform and then a netPI for the software deployment later, don't you think.
Now back to your question how to develop containers for netPI. First rule: for pulling images from somewhere you need in all cases a registry server.
1. First method is to host your container on Docker hub registry server ... like we as Hilscher do it with all the example containers like the HDMI for example. You can create an own repository in minutes there. If you like you can link the repository to a github source pool containing the Docker buildscript "Dockerfile" and then Docker hub is able to build a container directly on the web automated. Of course this makes all the sources open and is not always what is intended
2. Second method is creating an own trusted registry server locally on a Linux machine. How to do that is described here: https://docs.docker.com/registry/deploying/. You can also host a registry server on a Raspberry Pi ... how to do that is described in the forum here step by step: https://forum.hilscher.com/thread-291.html.
So a Rpi can be the development platform and a registry server all in one device. Once you have a registry server running on a Rpi you can just call "docker push" to push your container on the same machine you developed it on and then netPI is able to pull it from there. On latest software version of netPI you can directly setup registries in terms of ip address, names and password if required next of the default registry "DockerHub". For a trusted Registry it is necessary to install the certificates on netPI, else netPI will not pull anything.
Thx
Armin
the story about netPI is special ... we tell customer indeed to collect experience with Docker and building own containers and starting/testing the software on a standard Rpi3 (at $30cost) and then if all the software has been passed the tests to buy a professional netPI afterwards which is a Docker Host only to run the software securely and not a development platform. So it is a fair offer to have a standard Rpi3 as development platform and then a netPI for the software deployment later, don't you think.
Now back to your question how to develop containers for netPI. First rule: for pulling images from somewhere you need in all cases a registry server.
1. First method is to host your container on Docker hub registry server ... like we as Hilscher do it with all the example containers like the HDMI for example. You can create an own repository in minutes there. If you like you can link the repository to a github source pool containing the Docker buildscript "Dockerfile" and then Docker hub is able to build a container directly on the web automated. Of course this makes all the sources open and is not always what is intended
2. Second method is creating an own trusted registry server locally on a Linux machine. How to do that is described here: https://docs.docker.com/registry/deploying/. You can also host a registry server on a Raspberry Pi ... how to do that is described in the forum here step by step: https://forum.hilscher.com/thread-291.html.
So a Rpi can be the development platform and a registry server all in one device. Once you have a registry server running on a Rpi you can just call "docker push" to push your container on the same machine you developed it on and then netPI is able to pull it from there. On latest software version of netPI you can directly setup registries in terms of ip address, names and password if required next of the default registry "DockerHub". For a trusted Registry it is necessary to install the certificates on netPI, else netPI will not pull anything.
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
