June-29th-2018, 10:47 AM
Well Flo, I am running into the same problem.
I know it worked in one of the first releases of netPI definitively to use Docker daemon in a container (Docker in Docker). But the current restrictions of netPI's Host Docker in the latest released prohibits apparently using Docker in a container full featured nowadays.
Especially the cgroups that have been mounted on the Host Docker are making a problem here to grant full access in a container. I am sorry to say that I have no solution for that problem. The container development example container is useless.
There are only two options I see.
1.) use an original raspberry PI 3 for developments as the netPIs principle concept recommends it where you have full access to the Docker
2.) generate a Docker project on Docker hub/github yourself and let it generate automated there like we do it with all examples.
I know it worked in one of the first releases of netPI definitively to use Docker daemon in a container (Docker in Docker). But the current restrictions of netPI's Host Docker in the latest released prohibits apparently using Docker in a container full featured nowadays.
Especially the cgroups that have been mounted on the Host Docker are making a problem here to grant full access in a container. I am sorry to say that I have no solution for that problem. The container development example container is useless.
There are only two options I see.
1.) use an original raspberry PI 3 for developments as the netPIs principle concept recommends it where you have full access to the Docker
2.) generate a Docker project on Docker hub/github yourself and let it generate automated there like we do it with all examples.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)