-
Notifications
You must be signed in to change notification settings - Fork 95
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
Incorrect host IP for Windows + WSL2 #294
Comments
Hello, thank you for reporting this issue! 👍 As you can see in the |
Could you please share the exact log message? It would help to identify why exactly it decided to use this value. Thanks! 🙏 |
I’m not sure I understand what is the exact message that you are referring
to
On Fri 30. Apr 2021 at 16:09, Michal Augustýn ***@***.***> wrote:
Could you please share the exact log message? It would help to identify
why exactly it decided to use this value. Thanks! 🙏
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#294 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB6TLY3GXMEKDAJSFEGRRDTLK2Y5ANCNFSM434E2WNQ>
.
--
Best regards,
Eugene Petrenko
https://jonnyzzz.com
|
The log message coming from getContainerHost method, you linked in your first message. So e.g. something like |
I'm seeing the same issue with WSL2. This is the output from gradle :
Similar to jonnyzzz ,
gets it to work OK docker inspect output for the network settings is :
|
Same issue here fwiw:
I'd be happy to debug this since I have it reproduced. lmk if that would be helpful. |
Hello @dboreham , it would be great if you could share the output of I'm asking for this because if I understand the issue right, we should detect the WSL network and then use |
Will do that when I have a minute. WSL2 is different in that the kernel(s) magically map ports into the host. So the peer address seen by the container isn't actually the host. |
Yeah, getting the right Please share the whole output of the |
inspect_network.json:
inspect_db.json:
inspect_service.json:
|
I just want to be sure...are you in the same situation as the original reported, so do you execute Gradle inside WSL? The issue is that those inspections are the same, regardless of whether you are querying them from Windows or WSL. So what we actually need is to detect that we are running inside WSL, and use Are you aware of any reliable way how to achieve this? I have zero experience with WSL so far :( |
Hmm...yes that makes sense since the docker daemon itself is running on Windows native. Generally WSL2 will always claim it is Linux. I ran this gradle code:
it says:
|
Cool! It looks like we could use this. I will prepare a PR tomorrow. Thank you very much for you assistance! 👍 |
Hello, I'm trying to publish the new version of the plugin but Sonatype is still timeouting, so without success so far 😢 |
Hi, wondering if could try again to push this release? Thanks. |
It is already released, as |
Hmm...my build isn't resolving that version (but it does find 0.4.11). I will dig into where it gets it from... |
Perhaps I should ask: which repo should we expect to find it in? |
Ah, you're right. There was an issue with publishing to Maven Central and it was handled manually but the publishing to the Gradle Plugin Portal wasn't handled. I will fix this, and you can use the binaries from Maven Central as described in README in the meantime. Sorry for the inconvenience. |
Ah, I think I see now what's happening: in my build gradle is configured to use both Maven Central and gradle plugins repos. It presumably checks the plugins repo first and resolves the old version, then never checks Maven Central. I think there's some magic incantation you can use to force it to check the right repo... |
I'm using the plugin in Gradle inside WSL2 ubuntu instance on Windows.
The TCP probing feature was using the incorrect IP of to probe-started containers.
The workaround was to set the
SERVICES_HOST=0.0.0.0
before starting the Gradle build.It looks like the code does not work correctly for such a setup (Windows + WSL2, running in WSL2)
The text was updated successfully, but these errors were encountered: