Etcd: Error while running etcd v3 on Docker

Created on 20 Dec 2016 · 11Comments · Source: etcd-io/etcd

When I try to run etcd (version 3.0.0) on Docker:

sudo docker run -d -v /usr/share/ca-certificates/:/etc/ssl/certs -p 4001:4001 -p 2380:2380 -p 2379:2379 \
 --name etcd quay.io/coreos/etcd:v3.0.0  \
 -name etcd0 \
 -advertise-client-urls http://${HostIP}:2379,http://${HostIP}:4001 \
 -listen-client-urls http://0.0.0.0:2379,http://0.0.0.0:4001 \
 -initial-advertise-peer-urls http://${HostIP}:2380 \
 -listen-peer-urls http://0.0.0.0:2380 \
 -initial-cluster-token etcd-cluster-1 \
 -initial-cluster etcd0=http://${HostIP}:2380 \
 -initial-cluster-state new

I have an error:

docker: Error response from daemon: invalid header field value "oci runtime error: container_linux.go:247: starting container process caused \"exec: \\\"-name\\\": executable file not found in $PATH\"\n".

What is the reason of this error and how I can fix it?

Source

romach

Most helpful comment

Ok this works. You need to specify the binary path in container image.

sudo docker run --name etcd0 quay.io/coreos/etcd:v3.0.0 \ 
    /etcd \
    --name my-etcd-1 \
    --listen-client-urls http://localhost:2379 \
    --advertise-client-urls http://localhost:2379 \
    --listen-peer-urls http://localhost:2380 \
    --initial-advertise-peer-urls http://localhost:2380 \
    --initial-cluster my-etcd-1=http://localhost:2380 \
    --initial-cluster-token my-etcd-token \
    --initial-cluster-state new

sudo docker run --name etcd0 quay.io/coreos/etcd:v3.1.0-rc.1 \
    /usr/local/bin/etcd \
    --name my-etcd-1 \
    --data-dir /var/lib/etcd \
    --listen-client-urls http://localhost:2379 \
    --advertise-client-urls http://localhost:2379 \
    --listen-peer-urls http://localhost:2380 \
    --initial-advertise-peer-urls http://localhost:2380 \
    --initial-cluster my-etcd-1=http://localhost:2380 \
    --initial-cluster-token my-etcd-token \
    --initial-cluster-state new

gyuho on 21 Dec 2016

👍4

All 11 comments

This looks like Docker error? It works for me

sudo docker run --name etcd0 quay.io/coreos/etcd:v3.0.0

My docker version is 1.12.5

gyuho on 20 Dec 2016

@gyuho It is working for you because you are not passing any arguments (like -listen-peer-urls).

You need to run the command like this till coreos fixes the issue:

docker run -d --name etcd --net host --entrypoint=/usr/local/bin/etcd quay.io/coreos/etcd:latest --listen-peer-urls 'http://0.0.0.0:2380' --listen-client-urls 'http://0.0.0.0:2379' --advertise-client-urls 'http://xxx.xxx.xxx.xxx:2379'

gourao on 21 Dec 2016

Ok this works. You need to specify the binary path in container image.

sudo docker run --name etcd0 quay.io/coreos/etcd:v3.0.0 \ 
    /etcd \
    --name my-etcd-1 \
    --listen-client-urls http://localhost:2379 \
    --advertise-client-urls http://localhost:2379 \
    --listen-peer-urls http://localhost:2380 \
    --initial-advertise-peer-urls http://localhost:2380 \
    --initial-cluster my-etcd-1=http://localhost:2380 \
    --initial-cluster-token my-etcd-token \
    --initial-cluster-state new

sudo docker run --name etcd0 quay.io/coreos/etcd:v3.1.0-rc.1 \
    /usr/local/bin/etcd \
    --name my-etcd-1 \
    --data-dir /var/lib/etcd \
    --listen-client-urls http://localhost:2379 \
    --advertise-client-urls http://localhost:2379 \
    --listen-peer-urls http://localhost:2380 \
    --initial-advertise-peer-urls http://localhost:2380 \
    --initial-cluster my-etcd-1=http://localhost:2380 \
    --initial-cluster-token my-etcd-token \
    --initial-cluster-state new

gyuho on 21 Dec 2016

👍4

@romach @gourao Any feedback on specifying the exec path in the docker commands?
Please let us know if you have any other concerns. Thanks.

gyuho on 27 Dec 2016

@gyuho is this documented anywhere, ask as in most places I see documentation for v2 for which it does not expect the binary path.

bhujangr on 18 Jan 2017

@bhujangr You can find more docs at https://github.com/coreos/etcd/blob/master/Documentation/op-guide/container.md.

gyuho on 18 Jan 2017

👍1

The document on coreos.com is not correct: doc.

hyfrey on 6 Feb 2017

😕2

still not fixed

mcwienczek on 21 May 2017

👍1

@VsMax what's not fixed?

https://coreos.com/etcd/docs/latest/v2/docker_guide.html seems out of date; https://github.com/coreos/etcd/blob/master/Documentation/v2/docker_guide.md now forces the docker tag to v2.3.x so that the v2 docker guide is pinned to 2.x behavior

heyitsanthony on 22 May 2017

If it's out of date why it says /docs/latest?
Where can I find documentation regarding running etcd v3 in docker?
I have read a lot of coreos documentation and unfortunately with each artcle I am more and more confused how to setup a cluster:

one tutorial uses etcd v2, other v3
it is recommended to use ignition config, yet transpiler is very hard to find and use
Don't know when and how to use (and debug) container linux config and when should I use ignition file( some kubernetes tutorials actually use container config file, not transpiled igntion file to setup a cluster).

I have to say it's all very confusing

mcwienczek on 23 May 2017