Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
vkravets opened this issue Jan 25, 2024 · 0 comments
Open

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

vkravets opened this issue Jan 25, 2024 · 0 comments

Comments

@vkravets
Copy link

vkravets commented Jan 25, 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
Screenshot 2024-01-29 at 20 44 31

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.

@vkravets vkravets changed the title [Enhancement]: Add ability to custom ryuk container [Enhancement]: Add ability to customize ryuk container Jan 29, 2024
@vkravets vkravets changed the title [Enhancement]: Add ability to customize ryuk container [Enhancement]: Add ability to supply network to ryuk container Jan 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants