-
Notifications
You must be signed in to change notification settings - Fork 61
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
publish to specified ip? #194
Comments
Could be a bug. Can you paste the relevant line from your crane config and the output that Crane gives you if you run it in verbose mode ( |
Close due to inactivity. Please reopen if this is still an issue. |
Hi I'm facing the same issue here with the latest version (2.5.2): I specifically bind an exposed port to the host loopback, but it looks like it's ignored by crane (running container exposed port ends up not mapped at all). I'm also running Docker with My configuration is: containers:
ghost-XXX:
image: "ghost:0.7.6"
volume:
- "/etc/localtime:/etc/localtime:ro"
- "/home/marc/www/XXX/ghost:/var/lib/ghost"
publish:
- "127.0.0.1:2368:2368" Creating then starting the container:
If I create the container manually it works and binds the port on the specified host address. Let me know if you need me to provide more details. |
@falzm
Lack of warning when parameters are in the wrong section is a known problem :( |
Oh well... Thank you, works much better indeed :) |
Hi!
I tried to publish elasticsearch to 127.0.0.1:9200:9200 but it's still published to 0.0.0.0 how can I avoid this? docker run with --iptables=true --icc=false options..
Any idea?
The text was updated successfully, but these errors were encountered: