-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Docker for Mac - cannot connect to Ryuk #1623
Comments
It looks like this might be a related problem: https://forums.docker.com/t/port-forward-not-working-on-a-macos-installation-but-works-on-others/77401 After reaching the broken state, I experience identical symptoms to the author of this forum post - exposed ports are broken for any container I launch. |
There are all sorts of similar-sounding issues, but this looks most similar: docker/for-mac#3487 Maybe there's a fix due imminently? docker/for-mac#3487 (comment) |
It seems that using the Edge version of Docker (2.0.5.0 (35318)) resolves this issue. Hopefully this will be released as Stable soon. I'll close this, as it is not a Testcontainers bug. |
I'm seeing this issue again on Docker Desktop for Mac v2.4.0.0 and Catalina 10.15.7 - anybody else or is it just me?
|
@AndreasEK see #3166 |
ok, upgrading testcontainers to 1.15.0-rc2 solved the issue, 1.14.3 still showed it. |
I believe that this is most likely a problem with Docker for Mac's userland proxy but am creating a ticket here for initial notes and visibility.
In the last couple of days I've noticed the following test failure on a Mac:
Various observations:
docker system prune
makes no difference.On this machine I have Docker Desktop for Mac, Version 2.0.0.3 (31259) - stable version.
This happens after I have run a sufficient number of testcontainers builds (not that many; maybe 5-20?). I can't narrow down a repro case further yet.
I tried to trigger this problem with the following bash snippet, but it did not reoccur:
The text was updated successfully, but these errors were encountered: