-
Notifications
You must be signed in to change notification settings - Fork 45
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
bind(): Cannot assign requested address #8
Comments
Hi, Could you provide the full spec of It seems it's varnish issue rather then docker image issue, but I might be wrong here. ;) |
I'm getting the same issue. Just try this and you get the error too:
This is with the latest Docker for Mac:
|
I hit the same error and got thrown off by it thinking it was a firewall issue. The bind error is most likely due to the fact that varnish cannot bind to ipv6 because there is no ipv6 local address in this docker image:
I'm guessing the bind error won't show if there is an inet6 available. |
Getting the same error. |
As far as I've noticed, it does not require IPv6 and the error can safely be ignored. |
I gave up on this and built my own image: |
@pumba-lt Thanks, although this probably off semi-offtopic; I think you fixed the "notice" in your image (which doesn't seem to be a problem) by specifying the Varnish seems to assume there's always an ipv6 interface and shows |
Well, it didn't work for me either - with -a or without -a. My command line was:
where, The output was:
It's not a fatal error, I agree, but I personally don't like to get any nonsense notices... Going to build my own image. |
When running from
docker-compose
, I get the following:Any idea what the problem with
bind()
is?The text was updated successfully, but these errors were encountered: