Failed to start vulcan service

[amacgregor]

Hi,

I keep getting this error when trying to start the service on a DigitalOcean CoreOs cluster with 3 nodes.

Any ideas of what might be wrong ?

Logs begin at Thu 2014-10-23 22:08:24 UTC, end at Fri 2014-10-24 02:11:52 UTC. --
Oct 24 02:11:42 cluster02 docker[1570]: Error response from daemon: No such container: vulcan1
Oct 24 02:11:42 cluster02 docker[1570]: 2014/10/24 02:11:42 Error: failed to remove one or more containers
Oct 24 02:11:42 cluster02 docker[1585]: Pulling repository mailgun/vulcand
Oct 24 02:11:43 cluster02 systemd[1]: Started Vulcan.
Oct 24 02:11:43 cluster02 docker[1596]: Service exited with error: service start failure: 501: All the given peers are not reachable (Tried to connect to each peer twice and failed) [0]
Oct 24 02:11:43 cluster02 systemd[1]: vulcan.service: main process exited, code=exited, status=255/n/a
Oct 24 02:11:43 cluster02 docker[1658]: Error response from daemon: No such container: vulcan1
Oct 24 02:11:43 cluster02 docker[1658]: 2014/10/24 02:11:43 Error: failed to kill one or more containers
Oct 24 02:11:43 cluster02 systemd[1]: vulcan.service: control process exited, code=exited status=1
Oct 24 02:11:43 cluster02 systemd[1]: Unit vulcan.service entered failed state.

[sym3tri]

It looks like vulcand is unable to connect to etcd from within its
container. It's probably easiest to run vulcand with the --net=host flag.

If that doesn't work try manually reading/writing keys in etcd using
etcdctl to see if etcd is running.

On Thu, Oct 23, 2014 at 7:15 PM, Allan MacGregor notifications@github.com
wrote:

Hi,

I keep getting this error when trying to start the service on a
DigitalOcean CoreOs cluster with 3 nodes.

Any ideas of what might be wrong ?

Logs begin at Thu 2014-10-23 22:08:24 UTC, end at Fri 2014-10-24 02:11:52 UTC. --
Oct 24 02:11:42 cluster02 docker[1570]: Error response from daemon: No such container: vulcan1
Oct 24 02:11:42 cluster02 docker[1570]: 2014/10/24 02:11:42 Error: failed to remove one or more containers
Oct 24 02:11:42 cluster02 docker[1585]: Pulling repository mailgun/vulcand
Oct 24 02:11:43 cluster02 systemd[1]: Started Vulcan.
Oct 24 02:11:43 cluster02 docker[1596]: Service exited with error: service start failure: 501: All the given peers are not reachable (Tried to connect to each peer twice and failed) [0]
Oct 24 02:11:43 cluster02 systemd[1]: vulcan.service: main process exited, code=exited, status=255/n/a
Oct 24 02:11:43 cluster02 docker[1658]: Error response from daemon: No such container: vulcan1
Oct 24 02:11:43 cluster02 docker[1658]: 2014/10/24 02:11:43 Error: failed to kill one or more containers
Oct 24 02:11:43 cluster02 systemd[1]: vulcan.service: control process exited, code=exited status=1
Oct 24 02:11:43 cluster02 systemd[1]: Unit vulcan.service entered failed state.

—
Reply to this email directly or view it on GitHub
#4.

[amacgregor]

Ed,

I tried doing that and I got the following error:

Oct 24 18:39:49 cluster02 systemd[1]: Starting Vulcan...
Oct 24 18:39:49 cluster02 docker[4010]: Error response from daemon: No such
container: vulcan1
Oct 24 18:39:49 cluster02 docker[4010]: 2014/10/24 18:39:49 Error: failed
to kill one or more containers
Oct 24 18:39:49 cluster02 docker[4021]: Error response from daemon: No such
container: vulcan1
Oct 24 18:39:49 cluster02 docker[4021]: 2014/10/24 18:39:49 Error: failed
to remove one or more containers
Oct 24 18:39:49 cluster02 docker[4036]: Pulling repository mailgun/vulcand
Oct 24 18:39:50 cluster02 systemd[1]: Started Vulcan.
Oct 24 18:39:50 cluster02 docker[4047]: flag provided but not defined: -net
Oct 24 18:39:50 cluster02 docker[4047]: Usage of /opt/vulcan/vulcand:
Oct 24 18:39:50 cluster02 docker[4047]: -apiInterface="": Interface to for
API to bind to
Oct 24 18:39:50 cluster02 docker[4047]: -apiPort=8182: Port to provide api
on
Oct 24 18:39:50 cluster02 docker[4047]: -certPath="": KeyPair to use
(enables TLS)
Oct 24 18:39:50 cluster02 docker[4047]: -endpointDialTimeout=5s: Endpoint
dial timeout
Oct 24 18:39:50 cluster02 docker[4047]: -endpointReadTimeout=50s: Endpoint
read timeout
Oct 24 18:39:50 cluster02 docker[4047]: -etcd=[]: Etcd discovery service
API endpoints
Oct 24 18:39:50 cluster02 docker[4047]: -etcdConsistency="STRONG": Etcd
consistency
Oct 24 18:39:50 cluster02 docker[4047]: -etcdKey="vulcand": Etcd key for
storing configuration
Oct 24 18:39:50 cluster02 docker[4047]: -interface="": Interface to bind to
Oct 24 18:39:50 cluster02 docker[4047]: -log="console": Logging to use
(syslog or console)
Oct 24 18:39:50 cluster02 docker[4047]: -logSeverity=WARN: logs at or above
this level to the logging output
Oct 24 18:39:50 cluster02 docker[4047]: -pidPath="": Path to write PID file
to
Oct 24 18:39:50 cluster02 docker[4047]: -port=8181: Port to listen on
Oct 24 18:39:50 cluster02 docker[4047]: -readTimeout=1m0s: HTTP server read
timeout (deprecated)
Oct 24 18:39:50 cluster02 docker[4047]: -sealKey="": Seal key used to store
encrypted data in the backend
Oct 24 18:39:50 cluster02 docker[4047]: -serverMaxHeaderBytes=1048576:
Maximum size of request headers
Oct 24 18:39:50 cluster02 docker[4047]: -serverReadTimeout=1m0s: HTTP
server read timeout
Oct 24 18:39:50 cluster02 docker[4047]: -serverWriteTimeout=1m0s: HTTP
server write timeout
Oct 24 18:39:50 cluster02 docker[4047]: -statsdAddr="": Statsd address in
form of 'host:port'
Oct 24 18:39:50 cluster02 docker[4047]: -statsdPrefix="": Statsd prefix
will be appended to the metrics emitted by this instance
Oct 24 18:39:50 cluster02 docker[4047]: -writeTimeout=1m0s: HTTP server
write timeout (deprecated)
Oct 24 18:39:50 cluster02 systemd[1]: vulcan.service: main process exited,
code=exited, status=2/INVALIDARGUMENT
Oct 24 18:39:50 cluster02 docker[4107]: Error response from daemon: No such
container: vulcan1
Oct 24 18:39:50 cluster02 docker[4107]: 2014/10/24 18:39:50 Error: failed
to kill one or more containers
Oct 24 18:39:50 cluster02 systemd[1]: vulcan.service: control process
exited, code=exited status=1
Oct 24 18:39:50 cluster02 systemd[1]: Unit vulcan.service entered failed
state.

On Fri, Oct 24, 2014 at 1:07 PM, Ed Rooth notifications@github.com wrote:

It looks like vulcand is unable to connect to etcd from within its
container. It's probably easiest to run vulcand with the --net=host
flag.

If that doesn't work try manually reading/writing keys in etcd using
etcdctl to see if etcd is running.

On Thu, Oct 23, 2014 at 7:15 PM, Allan MacGregor notifications@github.com

wrote:

Hi,

I keep getting this error when trying to start the service on a
DigitalOcean CoreOs cluster with 3 nodes.

Any ideas of what might be wrong ?

Logs begin at Thu 2014-10-23 22:08:24 UTC, end at Fri 2014-10-24
02:11:52 UTC. --
Oct 24 02:11:42 cluster02 docker[1570]: Error response from daemon: No
such container: vulcan1
Oct 24 02:11:42 cluster02 docker[1570]: 2014/10/24 02:11:42 Error:
failed to remove one or more containers
Oct 24 02:11:42 cluster02 docker[1585]: Pulling repository
mailgun/vulcand
Oct 24 02:11:43 cluster02 systemd[1]: Started Vulcan.
Oct 24 02:11:43 cluster02 docker[1596]: Service exited with error:
service start failure: 501: All the given peers are not reachable (Tried to
connect to each peer twice and failed) [0]
Oct 24 02:11:43 cluster02 systemd[1]: vulcan.service: main process
exited, code=exited, status=255/n/a
Oct 24 02:11:43 cluster02 docker[1658]: Error response from daemon: No
such container: vulcan1
Oct 24 02:11:43 cluster02 docker[1658]: 2014/10/24 02:11:43 Error:
failed to kill one or more containers
Oct 24 02:11:43 cluster02 systemd[1]: vulcan.service: control process
exited, code=exited status=1
Oct 24 02:11:43 cluster02 systemd[1]: Unit vulcan.service entered failed
state.

—
Reply to this email directly or view it on GitHub
#4.

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

[sym3tri]

Sorry, I should've been more explicit. The flag is for docker run, not
vulcand.

So it should be something like: docker run --net=host vulcand-container ...

More info here: https://docs.docker.com/reference/run/#network-settings

On Fri, Oct 24, 2014 at 11:42 AM, Allan MacGregor notifications@github.com
wrote:

Ed,

I tried doing that and I got the following error:

Oct 24 18:39:49 cluster02 systemd[1]: Starting Vulcan...
Oct 24 18:39:49 cluster02 docker[4010]: Error response from daemon: No
such
container: vulcan1
Oct 24 18:39:49 cluster02 docker[4010]: 2014/10/24 18:39:49 Error: failed
to kill one or more containers
Oct 24 18:39:49 cluster02 docker[4021]: Error response from daemon: No
such
container: vulcan1
Oct 24 18:39:49 cluster02 docker[4021]: 2014/10/24 18:39:49 Error: failed
to remove one or more containers
Oct 24 18:39:49 cluster02 docker[4036]: Pulling repository mailgun/vulcand
Oct 24 18:39:50 cluster02 systemd[1]: Started Vulcan.
Oct 24 18:39:50 cluster02 docker[4047]: flag provided but not defined:
-net
Oct 24 18:39:50 cluster02 docker[4047]: Usage of /opt/vulcan/vulcand:
Oct 24 18:39:50 cluster02 docker[4047]: -apiInterface="": Interface to for
API to bind to
Oct 24 18:39:50 cluster02 docker[4047]: -apiPort=8182: Port to provide api
on
Oct 24 18:39:50 cluster02 docker[4047]: -certPath="": KeyPair to use
(enables TLS)
Oct 24 18:39:50 cluster02 docker[4047]: -endpointDialTimeout=5s: Endpoint
dial timeout
Oct 24 18:39:50 cluster02 docker[4047]: -endpointReadTimeout=50s: Endpoint
read timeout
Oct 24 18:39:50 cluster02 docker[4047]: -etcd=[]: Etcd discovery service
API endpoints
Oct 24 18:39:50 cluster02 docker[4047]: -etcdConsistency="STRONG": Etcd
consistency
Oct 24 18:39:50 cluster02 docker[4047]: -etcdKey="vulcand": Etcd key for
storing configuration
Oct 24 18:39:50 cluster02 docker[4047]: -interface="": Interface to bind
to
Oct 24 18:39:50 cluster02 docker[4047]: -log="console": Logging to use
(syslog or console)
Oct 24 18:39:50 cluster02 docker[4047]: -logSeverity=WARN: logs at or
above
this level to the logging output
Oct 24 18:39:50 cluster02 docker[4047]: -pidPath="": Path to write PID
file
to
Oct 24 18:39:50 cluster02 docker[4047]: -port=8181: Port to listen on
Oct 24 18:39:50 cluster02 docker[4047]: -readTimeout=1m0s: HTTP server
read
timeout (deprecated)
Oct 24 18:39:50 cluster02 docker[4047]: -sealKey="": Seal key used to
store
encrypted data in the backend
Oct 24 18:39:50 cluster02 docker[4047]: -serverMaxHeaderBytes=1048576:
Maximum size of request headers
Oct 24 18:39:50 cluster02 docker[4047]: -serverReadTimeout=1m0s: HTTP
server read timeout
Oct 24 18:39:50 cluster02 docker[4047]: -serverWriteTimeout=1m0s: HTTP
server write timeout
Oct 24 18:39:50 cluster02 docker[4047]: -statsdAddr="": Statsd address in
form of 'host:port'
Oct 24 18:39:50 cluster02 docker[4047]: -statsdPrefix="": Statsd prefix
will be appended to the metrics emitted by this instance
Oct 24 18:39:50 cluster02 docker[4047]: -writeTimeout=1m0s: HTTP server
write timeout (deprecated)
Oct 24 18:39:50 cluster02 systemd[1]: vulcan.service: main process exited,
code=exited, status=2/INVALIDARGUMENT
Oct 24 18:39:50 cluster02 docker[4107]: Error response from daemon: No
such
container: vulcan1
Oct 24 18:39:50 cluster02 docker[4107]: 2014/10/24 18:39:50 Error: failed
to kill one or more containers
Oct 24 18:39:50 cluster02 systemd[1]: vulcan.service: control process
exited, code=exited status=1
Oct 24 18:39:50 cluster02 systemd[1]: Unit vulcan.service entered failed
state.

On Fri, Oct 24, 2014 at 1:07 PM, Ed Rooth notifications@github.com
wrote:

It looks like vulcand is unable to connect to etcd from within its
container. It's probably easiest to run vulcand with the --net=host
flag.

If that doesn't work try manually reading/writing keys in etcd using
etcdctl to see if etcd is running.

On Thu, Oct 23, 2014 at 7:15 PM, Allan MacGregor <
notifications@github.com>

wrote:

Hi,

I keep getting this error when trying to start the service on a
DigitalOcean CoreOs cluster with 3 nodes.

Any ideas of what might be wrong ?

Logs begin at Thu 2014-10-23 22:08:24 UTC, end at Fri 2014-10-24
02:11:52 UTC. --
Oct 24 02:11:42 cluster02 docker[1570]: Error response from daemon: No
such container: vulcan1
Oct 24 02:11:42 cluster02 docker[1570]: 2014/10/24 02:11:42 Error:
failed to remove one or more containers
Oct 24 02:11:42 cluster02 docker[1585]: Pulling repository
mailgun/vulcand
Oct 24 02:11:43 cluster02 systemd[1]: Started Vulcan.
Oct 24 02:11:43 cluster02 docker[1596]: Service exited with error:
service start failure: 501: All the given peers are not reachable (Tried
to
connect to each peer twice and failed) [0]
Oct 24 02:11:43 cluster02 systemd[1]: vulcan.service: main process
exited, code=exited, status=255/n/a
Oct 24 02:11:43 cluster02 docker[1658]: Error response from daemon: No
such container: vulcan1
Oct 24 02:11:43 cluster02 docker[1658]: 2014/10/24 02:11:43 Error:
failed to kill one or more containers
Oct 24 02:11:43 cluster02 systemd[1]: vulcan.service: control process
exited, code=exited status=1
Oct 24 02:11:43 cluster02 systemd[1]: Unit vulcan.service entered
failed
state.

—
Reply to this email directly or view it on GitHub
#4.

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

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

[amacgregor]

I tried that, same result.

Oct 25 13:19:24 cluster02 systemd[1]: Starting Vulcan...
Oct 25 13:19:24 cluster02 docker[11253]: Error response from daemon: No such container: vulcan1
Oct 25 13:19:24 cluster02 docker[11253]: 2014/10/25 13:19:24 Error: failed to kill one or more containers
Oct 25 13:19:24 cluster02 docker[11263]: Error response from daemon: No such container: vulcan1
Oct 25 13:19:24 cluster02 docker[11263]: 2014/10/25 13:19:24 Error: failed to remove one or more containers
Oct 25 13:19:24 cluster02 docker[11277]: Pulling repository mailgun/vulcand
Oct 25 13:19:25 cluster02 systemd[1]: Started Vulcan.
Oct 25 13:19:25 cluster02 docker[11288]: Service exited with error: service start failure: 501: All the given peers are not reachable (Tried to connect to each peer twice and failed) [0]
Oct 25 13:19:25 cluster02 systemd[1]: vulcan.service: main process exited, code=exited, status=255/n/a
Oct 25 13:19:25 cluster02 docker[11309]: Error response from daemon: No such container: vulcan1
Oct 25 13:19:25 cluster02 docker[11309]: 2014/10/25 13:19:25 Error: failed to kill one or more containers
Oct 25 13:19:25 cluster02 systemd[1]: vulcan.service: control process exited, code=exited status=1
Oct 25 13:19:25 cluster02 systemd[1]: Unit vulcan.service entered failed state.

For whatever reason vulcand doesn't seem to be able to use the docker interface to talk with etcd; which is indeed running:

core@cluster02 ~/unit-examples/blog-vulcan-example $ systemctl status etcd
â—� etcd.service - etcd
   Loaded: loaded (/usr/lib64/systemd/system/etcd.service; static)
  Drop-In: /run/systemd/system/etcd.service.d
           └─20-cloudinit.conf
   Active: active (running) since Thu 2014-10-23 22:08:58 UTC; 1 day 15h ago
 Main PID: 611 (etcd)
   CGroup: /system.slice/etcd.service
           └─611 /usr/bin/etcd

Oct 25 04:30:01 cluster02 etcd[611]: [etcd] Oct 25 04:30:01.808 INFO      | a0778a2b3240467cba42f51a78c4e66c: snapshot of 10006 events at index 320189 completed
Oct 25 05:27:32 cluster02 etcd[611]: [etcd] Oct 25 05:27:32.011 INFO      | a0778a2b3240467cba42f51a78c4e66c: snapshot of 10005 events at index 330194 completed
Oct 25 06:25:02 cluster02 etcd[611]: [etcd] Oct 25 06:25:02.208 INFO      | a0778a2b3240467cba42f51a78c4e66c: snapshot of 10005 events at index 340199 completed
Oct 25 07:22:32 cluster02 etcd[611]: [etcd] Oct 25 07:22:32.429 INFO      | a0778a2b3240467cba42f51a78c4e66c: snapshot of 10006 events at index 350205 completed
Oct 25 08:20:02 cluster02 etcd[611]: [etcd] Oct 25 08:20:02.649 INFO      | a0778a2b3240467cba42f51a78c4e66c: snapshot of 10005 events at index 360210 completed
Oct 25 09:17:32 cluster02 etcd[611]: [etcd] Oct 25 09:17:32.889 INFO      | a0778a2b3240467cba42f51a78c4e66c: snapshot of 10006 events at index 370216 completed
Oct 25 10:15:03 cluster02 etcd[611]: [etcd] Oct 25 10:15:03.111 INFO      | a0778a2b3240467cba42f51a78c4e66c: snapshot of 10005 events at index 380221 completed
Oct 25 11:12:33 cluster02 etcd[611]: [etcd] Oct 25 11:12:33.376 INFO      | a0778a2b3240467cba42f51a78c4e66c: snapshot of 10005 events at index 390226 completed
Oct 25 12:10:03 cluster02 etcd[611]: [etcd] Oct 25 12:10:03.599 INFO      | a0778a2b3240467cba42f51a78c4e66c: snapshot of 10005 events at index 400231 completed
Oct 25 13:06:39 cluster02 etcd[611]: [etcd] Oct 25 13:06:39.831 INFO      | a0778a2b3240467cba42f51a78c4e66c: snapshot of 10003 events at index 410234 completed

[sym3tri]

What's the full command that you're using to start vulcan with?

On Sat, Oct 25, 2014 at 6:22 AM, Allan MacGregor notifications@github.com
wrote:

I tried that, same result.

Oct 25 13:19:24 cluster02 systemd[1]: Starting Vulcan...
Oct 25 13:19:24 cluster02 docker[11253]: Error response from daemon: No such container: vulcan1
Oct 25 13:19:24 cluster02 docker[11253]: 2014/10/25 13:19:24 Error: failed to kill one or more containers
Oct 25 13:19:24 cluster02 docker[11263]: Error response from daemon: No such container: vulcan1
Oct 25 13:19:24 cluster02 docker[11263]: 2014/10/25 13:19:24 Error: failed to remove one or more containers
Oct 25 13:19:24 cluster02 docker[11277]: Pulling repository mailgun/vulcand
Oct 25 13:19:25 cluster02 systemd[1]: Started Vulcan.
Oct 25 13:19:25 cluster02 docker[11288]: Service exited with error: service start failure: 501: All the given peers are not reachable (Tried to connect to each peer twice and failed) [0]
Oct 25 13:19:25 cluster02 systemd[1]: vulcan.service: main process exited, code=exited, status=255/n/a
Oct 25 13:19:25 cluster02 docker[11309]: Error response from daemon: No such container: vulcan1
Oct 25 13:19:25 cluster02 docker[11309]: 2014/10/25 13:19:25 Error: failed to kill one or more containers
Oct 25 13:19:25 cluster02 systemd[1]: vulcan.service: control process exited, code=exited status=1
Oct 25 13:19:25 cluster02 systemd[1]: Unit vulcan.service entered failed state.

For whatever reason vulcand doesn't seem to be able to use the docker
interface to talk with etcd; which is indeed running:

core@cluster02 ~/unit-examples/blog-vulcan-example $ systemctl status etcd
â— etcd.service - etcd
Loaded: loaded (/usr/lib64/systemd/system/etcd.service; static)
Drop-In: /run/systemd/system/etcd.service.d
└─20-cloudinit.conf
Active: active (running) since Thu 2014-10-23 22:08:58 UTC; 1 day 15h ago
Main PID: 611 (etcd)
CGroup: /system.slice/etcd.service
└─611 /usr/bin/etcd

Oct 25 04:30:01 cluster02 etcd[611]: [etcd] Oct 25 04:30:01.808 INFO | a0778a2b3240467cba42f51a78c4e66c: snapshot of 10006 events at index 320189 completed
Oct 25 05:27:32 cluster02 etcd[611]: [etcd] Oct 25 05:27:32.011 INFO | a0778a2b3240467cba42f51a78c4e66c: snapshot of 10005 events at index 330194 completed
Oct 25 06:25:02 cluster02 etcd[611]: [etcd] Oct 25 06:25:02.208 INFO | a0778a2b3240467cba42f51a78c4e66c: snapshot of 10005 events at index 340199 completed
Oct 25 07:22:32 cluster02 etcd[611]: [etcd] Oct 25 07:22:32.429 INFO | a0778a2b3240467cba42f51a78c4e66c: snapshot of 10006 events at index 350205 completed
Oct 25 08:20:02 cluster02 etcd[611]: [etcd] Oct 25 08:20:02.649 INFO | a0778a2b3240467cba42f51a78c4e66c: snapshot of 10005 events at index 360210 completed
Oct 25 09:17:32 cluster02 etcd[611]: [etcd] Oct 25 09:17:32.889 INFO | a0778a2b3240467cba42f51a78c4e66c: snapshot of 10006 events at index 370216 completed
Oct 25 10:15:03 cluster02 etcd[611]: [etcd] Oct 25 10:15:03.111 INFO | a0778a2b3240467cba42f51a78c4e66c: snapshot of 10005 events at index 380221 completed
Oct 25 11:12:33 cluster02 etcd[611]: [etcd] Oct 25 11:12:33.376 INFO | a0778a2b3240467cba42f51a78c4e66c: snapshot of 10005 events at index 390226 completed
Oct 25 12:10:03 cluster02 etcd[611]: [etcd] Oct 25 12:10:03.599 INFO | a0778a2b3240467cba42f51a78c4e66c: snapshot of 10005 events at index 400231 completed
Oct 25 13:06:39 cluster02 etcd[611]: [etcd] Oct 25 13:06:39.831 INFO | a0778a2b3240467cba42f51a78c4e66c: snapshot of 10003 events at index 410234 completed

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

[amacgregor]

fleetctl start vulcand.service 

and the service file is

[Unit]
Description=Vulcan
After=docker.service

[Service]
TimeoutStartSec=0
ExecStartPre=-/usr/bin/docker kill vulcan1
ExecStartPre=-/usr/bin/docker rm vulcan1
ExecStartPre=/usr/bin/docker pull mailgun/vulcand
ExecStart=/usr/bin/docker run --net="host" --rm --name vulcan1 -p 80:80 -p 8182:8182 mailgun/vulcand /opt/vulcan/vulcand -apiInterface="0.0.0.0" -interface="0.0.0.0" -etcd="http://172.17.42.1:4001" -port=80 -apiPort=8182
ExecStop=/usr/bin/docker kill vulcan1

I also tried different variations of the net command including bridge (which should be the default)

[sym3tri]

If you curl etcd are you getting a response?

curl -L http://172.17.42.1:4001/v2/keys/

On Mon, Oct 27, 2014 at 10:10 AM, Allan MacGregor notifications@github.com
wrote:

fleetctl start vulcand.service

and the service file is

[Unit]
Description=Vulcan
After=docker.service

[Service]
TimeoutStartSec=0
ExecStartPre=-/usr/bin/docker kill vulcan1
ExecStartPre=-/usr/bin/docker rm vulcan1
ExecStartPre=/usr/bin/docker pull mailgun/vulcand
ExecStart=/usr/bin/docker run --net="host" --rm --name vulcan1 -p 80:80 -p 8182:8182 mailgun/vulcand /opt/vulcan/vulcand -apiInterface="0.0.0.0" -interface="0.0.0.0" -etcd="http://172.17.42.1:4001" -port=80 -apiPort=8182
ExecStop=/usr/bin/docker kill vulcan1

I also tried different variations of the net command including bridge
(which should be the default)

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

[amacgregor]

Yup, as far as I can tell etcd is working properly in that cluster.

[sym3tri]

The next thing I would try is curling etcd from within the container. If
you're unable to do that it's a network configuration issue. If you are
able to do that it might be an issue with the version of vulcan you're
using, and might be worth filing an issue
https://github.com/mailgun/vulcand/issues.

On Mon, Oct 27, 2014 at 10:21 AM, Allan MacGregor notifications@github.com
wrote:

Yup, as far as I can tell etcd is working properly in that cluster.

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

[porjo]

@amacgregor looks lik #6 may fix your issue

I've been getting this error and found I needed to sleep for a couple of seconds prior to launching vulcand. It seems that the network is not ready in time for the connection back to etcd from the container!?