Thanks. Still a lot of abracadabra haha, but got some references now.
Docker is really nice when the images and containers are well set-up. The personal files or configs can be saved externally and used as input of containers. The containers hold the programs. So if you mess up something, you just deploy a new container from the image. Or if it turns out that a newer image version does not work as expected, you just restart the old container, based on the older image.
The benefits of Docker are poorly reaped for ADS-B software at this moment, it becomes problematic when image maintainers do not explicitly use version (number) tags. That’s why I am thinking to make one myself. Also like you said, the configuration just looks weird.
In theory it should also be super easy to deploy multi USB receivers on a single system, because you forward the USB device to a container. Just use the original container start command, adjust ip, port and usb device, and go. Then again, I for example don’t understand all the configs yet. Like what will happen if you use the fr24key at the same time in multiple instances, and all that kind of stuff. FA seems to use a smarter way of detecting instances, I am getting a lot of mails from my testing haha.
I tried it by the way, because I have 2 USB receivers. But /dev/bus/usb/001/??? numbers keep changing (using those because I don’t get /dev/ttyXYZ ones) after container starts/restarts/stops. Plus when one instance (container) was up, and the other came online, they both stopped receiving signals from the sky.
This whole thing is pretty annoying. I have a clear vision but getting there is a lot harder than expected due to weird behaviour and difficulty in understanding software.