CM may start selenoid container in different network than one of the browser containers

[matez0]

If I see well, cm starts the selenoid container in a wired-in network selenoid:

cm/selenoid/docker.go

Line 737 in 5a7f739

networkName = "selenoid"

cm/selenoid/docker.go

Line 793 in 5a7f739

Network: networkName,

But at the same time it is possible to configure a different network for the browser containers with -container-network:

cm/selenoid/docker.go

Line 779 in 5a7f739

if !contains(cmd, "-container-network") {

How can the selenoid container work together with a browser container, if they are not in the same docker network?

Why the network of the selenoid container is not configurable?

[vania-pooh]

@matez0 cm is a tool that just launches a Docker container with Selenoid in automated way and settings that are suitable for the majority of use cases. You can deliver the same installation manually with Docker Compose and a shell script. This is why network name is hard-coded. We don't have plans to make this configurable in CM.

[matez0]

Even if the docker network is not planned to be configurable, the selenoid network should be set to the value given in the -container-network to have a usable system.
This would take not much effort to fix, would not?

[vania-pooh]

@matez0 yes, that should be doable.