Skip to content
This repository has been archived by the owner on Jan 15, 2023. It is now read-only.

Why start "etcd" not "etcd2"? #8

Open
ernoaapa opened this issue Jul 10, 2016 · 2 comments
Open

Why start "etcd" not "etcd2"? #8

ernoaapa opened this issue Jul 10, 2016 · 2 comments

Comments

@ernoaapa
Copy link

Hi!
I were looking at your code as solution for building auto healing etcd cluster on top of ASG.

I started to wonder why you call etcd not etcd2? https://github.com/crewjam/etcd-aws/blob/master/etcd-aws.go#L213
At least when I check in CoreOS alpha (899.11.0) the etcd executable starts the older version and etcd2 the new.

@TaiSHiNet
Copy link

Might be outdated, I had to modify and recompile

@crewjam
Copy link
Owner

crewjam commented Jul 12, 2016

because in the Docker container we are carrying our own etcd which is version 2.

ref: https://github.com/crewjam/etcd-aws/blob/master/Makefile#L20

Not sure how to clear that up? perhaps build the etcd binary as etcd2?

PRs/suggestions welcome. :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants