-
-
Notifications
You must be signed in to change notification settings - Fork 211
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
Order of WireMockContainerBuilder WithX calls caused duplicate Networks in Configuration #1217
Comments
@epDugas |
See attached for console app demonstrating issue. |
Are you using Linux or Windows containers? |
@epDugas It should be fixed now, can you use preview version 1.6.10-ci-19504 |
Thanks @StefH !
Linux |
@epDugas |
Describe the bug
The order of the .WithX calls to WireMockContainerBuilder can cause duplicate Networks in Configuration.
Expected behavior:
Expected the order of WireMockContainerBuilder.WithX calls to not duplicate Networks in the Configuration.
Test to reproduce
WireMockContainerBuilder.WithNetwork(x);
WireMockContainerBuilder.WithMappings(x)
andWireMockContainerBuilder.WithWatchStaticMappings(true);
Other related info
This was observed when updating WireMock.net. Some previous working code failed, an exception was thrown because of the duplicate Network entries in:
https://github.com/testcontainers/testcontainers-dotnet/blob/develop/src/Testcontainers/Clients/ContainerConfigurationConverter.cs at line 30.
Changing the order of the .WithX calls resolved the issue.
The text was updated successfully, but these errors were encountered: