[Enhancement]: Add ability to supply network to ryuk container

Module

Core

Synopsis

This is required due to one aspect of rootless podman networking:

https://docs.podman.io/en/latest/markdown/podman-run.1.html#network-mode-net

This implies that network is not picked up when runnig podman in rooless mode thus making it impossible for ryuk to communicate with other containers even if they were started with --network=bridge network

Proposal

Tescontainer can run using custom network (auto created via Network.createNetwork() or external) and ryuk in this case cannot be customized to use the same custom network. Some environmet can have restrictions on default network, or even have different access to each other. In this case ryuk could not see the containers at all.

Since Testcontainer already has custom env varible to override some functionality will be great to have custom varible to define:

• custom expose port for ryuk
• custom network name which ryuk container should connect during creation

Workaround in this case disable ryuk only.

Empieza siguiendo la creación del contenedor de Ryuk y las anulaciones existentes de variables de entorno en el módulo Core. Confirma cómo se proporcionarían una red personalizada y un puerto expuesto, y después añade cobertura para que Ryuk se una a la red solicitada y sea accesible a través del puerto configurado.