You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
vkravets
changed the title
[Enhancement]: Add ability to custom ryuk container
[Enhancement]: Add ability to customize ryuk container
Jan 29, 2024
vkravets
changed the title
[Enhancement]: Add ability to customize ryuk container
[Enhancement]: Add ability to supply network to ryuk container
Jan 29, 2024
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
networkProposal
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:
Workaround in this case disable ryuk only.
The text was updated successfully, but these errors were encountered: