• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[SOLVED] Usage of overlay driver
#1
Is it possible to use overlay driver using current portainer version of netpi. Its not working for me. And this leads to my second question if we can initialize the netpi node as a swarm manager?
  Reply
#2
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.


You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply
#3
Hi Armin,
I am not sure if I understood it correctly but I am talking about the creation of the network in the docker engine using the overlay driver (Similar to bridge/host or macvlan drivers etc.). The container can then be connected to the virtual network when it runs but by default it is Bridge network.
Thanks
  Reply
#4
Ok. I thought more of real overlay drivers for USB devices or for raspberry HAT modules that are loaded during kernel boot.

If I follow the documentation https://docs.docker.com/network/macvlan/ I see that starting this capability needs some more parameters like "--subnet" "-o" and so on when starting a container. Today portainer.io web GUI does not support entering those parameters when a container started. So my conclusion is that it will not work with todays version.
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply
#5
I investigate the MACVLAN network option issue. MACVLAN option can only be provided by portainer if docker runs in swarm mode. But on netPI docker is not running in swarm mode and there is no intention to enable it. This is why MACVLAN will not be supported.
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  usage of hilschernetpi/netpi-netx-ethernet-lan is working but costs 25% cpu power Michael_d 7 156 March-9th-2018, 10:52 AM
Last Post: Michael_d
  Usage of Fieldbus in and out and FRAM read and write nodes Schranz 8 178 March-5th-2018, 05:42 PM
Last Post: Schranz

Forum Jump:


Users browsing this thread: 1 Guest(s)