July-8th-2021, 01:43 PM
(This post was last modified: July-8th-2021, 03:41 PM by Armin@netPI.)
Oh yes this is something coming from the restiction of the netPI Docker engine.
Any Linux device that is needed in a container like the /dev/tun ... on netPI needs to be mapped manually in the container start parameter.
It is the same thing as you need to configure in one of our other containers we are providing which is this one here https://hub.docker.com/r/hilschernetpi/n...hernet-lan. This is an example for you to see which device to map ... /dev/net/tun. So you need to redeploy your Raspbian container again with this device mapped and also I think you should make sure you activated the privileged mode too.
Thx
Armin
Any Linux device that is needed in a container like the /dev/tun ... on netPI needs to be mapped manually in the container start parameter.
It is the same thing as you need to configure in one of our other containers we are providing which is this one here https://hub.docker.com/r/hilschernetpi/n...hernet-lan. This is an example for you to see which device to map ... /dev/net/tun. So you need to redeploy your Raspbian container again with this device mapped and also I think you should make sure you activated the privileged mode too.
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
