-
-
Notifications
You must be signed in to change notification settings - Fork 214
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
Add support to bind to ip-address instead of only localhost #1100
Conversation
Sadly, this PR broke usage of standalone WireMock in docker. It spins up, but never answers the requests. Dowgraded one version (before this) - works just fine. We don't specify Urls, just the port. |
@nevaldas Because when I just start the latest WireMock Linux Container, it works fine:
|
My Docker Image provides the URL like this: You provide only the port? |
When running locally on my PC this works fine: var server = WireMockServer.Start(new WireMockServerSettings
{
Urls = new[] { "http://*:9091" },
StartAdminInterface = true
});
System.Console.WriteLine($"3: {string.Join(", ", server.Urls)}");
System.Console.WriteLine("Press any key to stop...");
System.Console.ReadKey();
server.Stop(); But in your case, when this same code is running inside a Docker container, it fails? |
Partially yes. If you would change given code to this and run it in Docker container, it would not respond anymore: var server = WireMockServer.Start(new WireMockServerSettings
{
Port = 9091,
StartAdminInterface = true
});
System.Console.WriteLine($"3: {string.Join(", ", server.Urls)}");
System.Console.WriteLine("Press any key to stop...");
System.Console.ReadKey();
server.Stop(); |
I can reproduce it. I think this PR will fix it: |
A new NuGet version 1.5.55 will be available in some time. |
No description provided.