connectable icon indicating copy to clipboard operation
connectable copied to clipboard

iptables command failing: address already in use

Open jasisk opened this issue 9 years ago • 12 comments

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

jasisk avatar Aug 07 '15 18:08 jasisk

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

progrium avatar Aug 07 '15 23:08 progrium

Yup. Those are from:

$ docker run -d --name connectable \
        -v /var/run/docker.sock:/var/run/docker.sock \
        gliderlabs/connectable:latest

jasisk avatar Aug 08 '15 01:08 jasisk

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

jasisk avatar Aug 08 '15 01:08 jasisk

Okay, but what about thirsty_mcclintock?

On Fri, Aug 7, 2015 at 8:32 PM, Jean-Charles Sisk [email protected] 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

progrium avatar Aug 08 '15 13:08 progrium

That's the result of this, no?

jasisk avatar Aug 08 '15 13:08 jasisk

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 [email protected] 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

progrium avatar Aug 08 '15 13:08 progrium

Ah. My mistake. :grinning:

jasisk avatar Aug 08 '15 14:08 jasisk

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

yangxuesong avatar Aug 17 '15 09:08 yangxuesong

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

raphink avatar Jan 14 '16 16:01 raphink

$ 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

raphink avatar Jan 14 '16 16:01 raphink

I am also encountering this issue.

calvn avatar Jan 18 '16 19:01 calvn

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

thomas-oo avatar Aug 07 '17 18:08 thomas-oo