-
Notifications
You must be signed in to change notification settings - Fork 88
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
Gateway timeout #25
Comments
Which host environment you're working with? |
Working with ubuntu 18.04 Yes I can both curl the host ip and ping the gateway name. No firewall in the way |
Strange. What are the logs of |
The logs where pretty normal:
I resolved dropping all the containers, removing all the docker-networks and start all over again. Sorry for bothering you. |
Glad to hear that.
…On Sat, 7 Sep 2019, 18:48 Luca Orlandi, ***@***.***> wrote:
The logs where pretty normal:
Docker Host: 172.20.0.1 (default gateway)
Forwarding ports: 0:65535
I resolved dropping all the containers, removing all the docker-networks
and start all over again.
It must have been a mess with the "real" networks (eth, wifi) and docker's
nets
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#25?email_source=notifications&email_token=AA6HUATBL4L6W2GER2QVF6LQIPLPRA5CNFSM4ITIN5LKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6E45XI#issuecomment-529125085>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA6HUASIKXXHVI2SSWIOPN3QIPLPRANCNFSM4ITIN5LA>
.
|
I cannot make the gateway work properly.
I've read #21 and bound my app to the host ip
172.20.0.1
(resulting fromdocker network inspect bridge --format='{{( index .IPAM.Config 0).Gateway}}'
).Relevant part of docker-compose.yml is:
Then I start the java api
mvn spring-boot:run
which listens on172.20.0.1
port8080
.From the host shell:
From the goomon/docker-host container:
From the linked container:
What's wrong in my config?
The text was updated successfully, but these errors were encountered: