February-16th-2018, 12:58 PM
I understand. In the case of the Fieldbus interfaces are used for Ethernet (layer 2) usage, or when the control protocol (like Modbus) is loaded at the Application level, I think the better option would be to expose them into docker as 3rd party network interfaces, via a plugin into the host.
This way, the running app into the docker image doesn't have to take care of the firmware / specific interface activation. It might be also possible then to bind the fieldbus interfaces to multiple docker images, perhaps make use of the "Overlay" and "Macvlan" networks into docker.
And also, you can then provide NetX firmware updates via the host firmware instead, add features when available...
This way, we can load a standard docker image, without touching the network part inside the image, and still benefit of the fieldbus interfaces.
This way, the running app into the docker image doesn't have to take care of the firmware / specific interface activation. It might be also possible then to bind the fieldbus interfaces to multiple docker images, perhaps make use of the "Overlay" and "Macvlan" networks into docker.
And also, you can then provide NetX firmware updates via the host firmware instead, add features when available...
This way, we can load a standard docker image, without touching the network part inside the image, and still benefit of the fieldbus interfaces.
