iptables command failing: address already in use

[jasisk]

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]

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

[jasisk]

Yup. Those are from:

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

[jasisk]

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

[progrium]

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
#21 (comment)
.

Jeff Lindsay
http://progrium.com

[jasisk]

That's the result of this, no?

[progrium]

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

connectable/connectable.go

Lines 41 to 51 in 7173eb2

	c, err := client.CreateContainer(docker.CreateContainerOptions{
	Config: &docker.Config{
	Image: image,
	Cmd: []string{cmd},
	Entrypoint: []string{"/bin/sh", "-c"},
	},
	HostConfig: &docker.HostConfig{
	Privileged: true,
	NetworkMode: fmt.Sprintf("container:%s", container),
	},
	})

,
no?

—
Reply to this email directly or view it on GitHub
#21 (comment)
.

Jeff Lindsay
http://progrium.com

[jasisk]

Ah. My mistake. 😀

[yangxuesong]

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

[raphink]

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

[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

[calvn]

I am also encountering this issue.

[thomas-oo]

#36 Fixed this issue for me