February-20th-2018, 08:23 AM
Well, netPI is not and will not be a development platform for containers. It is a Docker host only and we keep going with the strategy to offer a secure device where open features of Docker are definitively disabled, else an application in the container can get root rights of the host system and install a SSH connection for example to it which we don't want.
This strategy is of course only possible because netPI is compatible with the RPi3. This is an open system at nearly no cost (30EUR) and is THE development platform for netPI containers. Also we tell everybody not to buy a netPI, but a Raspberry Pi 3 instead first and to check if a software can be containerized and is working on RPi3 before using it on a netPI.
If you still want to insist to use netPI as a container development platform a use of the container https://hub.docker.com/r/hilschernetpi/n...vironment/ my be helpful. It is a containerized Docker (so Docker in Docker) and you can use the Docker CLI in this container. But still you can get access to the Docker Host socket on netPI with it.
Armin
This strategy is of course only possible because netPI is compatible with the RPi3. This is an open system at nearly no cost (30EUR) and is THE development platform for netPI containers. Also we tell everybody not to buy a netPI, but a Raspberry Pi 3 instead first and to check if a software can be containerized and is working on RPi3 before using it on a netPI.
If you still want to insist to use netPI as a container development platform a use of the container https://hub.docker.com/r/hilschernetpi/n...vironment/ my be helpful. It is a containerized Docker (so Docker in Docker) and you can use the Docker CLI in this container. But still you can get access to the Docker Host socket on netPI with it.
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
