July-18th-2018, 02:11 PM
Hello,
the question of an overlay driver/device trees is not a question of portainer/docker/container. An overlay driver on a Raspberry (netPI) is always a thing of the Host Linux depending on detected "parameters" set in the config.txt during the boot sequence. With those parameters the overlay drivers are loaded. A subsequent load of overlay drivers during runtine in a container/portainer is not possible.
The current version of portainer.io that you can test yourself on http://demo.portainer.io supports swarm technique. The version there is 1.18.1. On netPI we are currently using portainer.io in the version V1.12.4 that does not support swarm.
We have on the radar to switch portainer.io on netPI in future to the latest version. But the time schedule is not clear. I see a release by end of the year. So till then there is no swam supported.
the question of an overlay driver/device trees is not a question of portainer/docker/container. An overlay driver on a Raspberry (netPI) is always a thing of the Host Linux depending on detected "parameters" set in the config.txt during the boot sequence. With those parameters the overlay drivers are loaded. A subsequent load of overlay drivers during runtine in a container/portainer is not possible.
The current version of portainer.io that you can test yourself on http://demo.portainer.io supports swarm technique. The version there is 1.18.1. On netPI we are currently using portainer.io in the version V1.12.4 that does not support swarm.
We have on the radar to switch portainer.io on netPI in future to the latest version. But the time schedule is not clear. I see a release by end of the year. So till then there is no swam supported.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
