Skip to content

Feature Request: Allow Network Mode Selection in Container Structure Test #493

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

Open
Donatien26 opened this issue Mar 4, 2025 · 0 comments · May be fixed by #492
Open

Feature Request: Allow Network Mode Selection in Container Structure Test #493

Donatien26 opened this issue Mar 4, 2025 · 0 comments · May be fixed by #492

Comments

@Donatien26
Copy link

Description

With recent Docker installations, the default network mode is bridge, which prevents requests to networks not connected to the bridge. When using container-structure-test to send curl requests to different services, this limitation can cause issues.

Would it be possible to add an option to specify the desired network mode when running container-structure-test? This would allow users to configure a network mode that suits their testing environment, such as host or a custom network.

Expected Behavior

  • A new flag or configuration option to specify the network mode (--network similar to docker run).
  • Users can set host, bridge, or any custom network as needed.

Actual Behavior

  • Currently, the default bridge mode restricts network access, preventing some requests from working as expected.
  • No built-in option to override the network mode.

Use Case

  • This feature would benefit users testing containers that need access to external services, databases, or APIs that are not within the default bridge network.

Would this be a feasible addition to the tool? Thanks!

@Donatien26 Donatien26 linked a pull request Mar 4, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant