Rationale for having master builds in docker containers?

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Tomcsányi, Domonkos domi at tomcsanyi.net
Thu Dec 6 12:12:18 UTC 2018


Hi Neels,

2018. dec. 6. dátummal, 13:38 időpontban Neels Hofmeyr <nhofmeyr at sysmocom.de> írta:

> 
> Those are the projects that run the python-based external tests, which involve
> opening up VTY and CTRL ports among others, because we start up the program and
> interact with it on VTY and CTRL. That means each of those projects is not able
> to run tests more than once per slave, or we get sporadic conflicts of not
> being able to start the main program. That was really annoying.
> 
> Another complex way would be to round robin through a range of ports or
> localhost addresses or something, and tweak the .cfg for each test run so that
> the ports never conflict :/
> 
> Or some sort of network segmenting?

I think Linux network namespaces would be a possible solution for this issue, if I understood correctly, but setting that up feels to me more complicated then using Docker.
Just my 2cents.

Cheers,
Domi


More information about the OpenBSC mailing list