October-16th-2019, 01:00 PM
Hello Magnus,
Docker allows to specifiy mapped device and environment variables and other settings only during the first container start. So you have no chance to set those parameters afterwards. This is no a Hilscher restriction but a Docker one.
As described in the readme https://hub.docker.com/r/hilschernetpi/n...sys-basis/ you have to add at least the ENV variable "IP_ADDRESS" set to value "dhcp". And do not forget to map devices /dev/spidev0.0 and /dev/net/tun to the container.
A very cool thing with Docker Web GUI on netPI is that you can click on a running container and then "Duplicate/Edit". It then copy the current settings of your container and you can add more parameters if you want. When you deploy the container then, the old container will be deletet and a new one started.
But of course you already loaded CODESYS runtime is gone since the container is new.
Thx
armin
Docker allows to specifiy mapped device and environment variables and other settings only during the first container start. So you have no chance to set those parameters afterwards. This is no a Hilscher restriction but a Docker one.
As described in the readme https://hub.docker.com/r/hilschernetpi/n...sys-basis/ you have to add at least the ENV variable "IP_ADDRESS" set to value "dhcp". And do not forget to map devices /dev/spidev0.0 and /dev/net/tun to the container.
A very cool thing with Docker Web GUI on netPI is that you can click on a running container and then "Duplicate/Edit". It then copy the current settings of your container and you can add more parameters if you want. When you deploy the container then, the old container will be deletet and a new one started.
But of course you already loaded CODESYS runtime is gone since the container is new.
Thx
armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
