search

gliderlabs / connectable

Magic proxy for internal services
MIT License
464 stars 44 forks source link

iptables command failing: address already in use #21

Open jasisk opened 9 years ago

jasisk commented 9 years ago

connectable is presently failing during the iptables command:

$ docker logs connectable
2015/08/07 18:28:50 Connectable listening on 10000 ...
Self: 2011f14d0013ed337acf696b3def8737b45eb7d787b4de79e34b1294b8781e9d bridge
2015/08/07 18:28:51 non-zero exit: 1
$ docker logs thirsty_mcclintock
2015/08/07 18:28:51 listen tcp :10000: bind: address already in use
progrium commented 9 years ago

Can you share the docker runs that you used? What are you running?

jasisk commented 9 years ago

Yup. Those are from:

$ docker run -d --name connectable \
        -v /var/run/docker.sock:/var/run/docker.sock \
        gliderlabs/connectable:latest
jasisk commented 9 years ago

I also have resolvable, registrator, and consul running. Nothing is otherwise bound to 10000 anywhere.

progrium commented 9 years ago

Okay, but what about thirsty_mcclintock?

On Fri, Aug 7, 2015 at 8:32 PM, Jean-Charles Sisk notifications@github.com wrote:

I also have resolvable, registrator, and consul running. Nothing is otherwise bound to 10000 anywhere.

— Reply to this email directly or view it on GitHub https://github.com/gliderlabs/connectable/issues/21#issuecomment-128879544 .

Jeff Lindsay http://progrium.com

jasisk commented 9 years ago

That's the result of this, no?

progrium commented 9 years ago

Sure, but that was not clear at all. It doesn't name that container so it's randomly generated like any other container you might run.

On Sat, Aug 8, 2015 at 8:40 AM, Jean-Charles Sisk notifications@github.com wrote:

That' the result of this https://github.com/gliderlabs/connectable/blob/7173eb22885aa246516979b3b0fc5399fe70ca16/connectable.go#L41-L51, no?

— Reply to this email directly or view it on GitHub https://github.com/gliderlabs/connectable/issues/21#issuecomment-128982302 .

Jeff Lindsay http://progrium.com

jasisk commented 9 years ago

Ah. My mistake. :grinning:

yangxuesong commented 9 years ago

hi, the connectable container seems ok, but the second container logs error: listening on 10000... unable to find self

raphink commented 8 years ago

I'm currently seeing this too, even though I have no containers listening on 10000 apparently.

raphink commented 8 years ago 
$ netstat -nlp | grep 10000
$ docker run --name connectable -v /var/run/docker.sock:/var/run/docker.sock gliderlabs/connectable:latest
2016/01/14 16:15:30 Connectable listening on 10000 ...
Self: 015fa985c0a8822b4a029cca85960b3055a8a5d38f82085968fedd29932b4c50 default
2016/01/14 16:15:30 non-zero exit: 1
calvn commented 8 years ago

I am also encountering this issue.

thomas-oo commented 7 years ago

https://github.com/gliderlabs/connectable/issues/36 Fixed this issue for me