-
Notifications
You must be signed in to change notification settings - Fork 9.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
go get does build a binary... but the binary isn't particularly useful #986
Comments
+1, we're seeing this as well. It seems that running a minimal, single-node etcd is not as simple as ./etcd anymore. |
Yea, we must restore the |
I'm a bit confused. Right now there's literally no way to clone HEAD of Is there, in fact, a way to build |
@onsi The binary will not be useful as you described for a while. Please refer the email we sent in etcd-dev. |
@xiangli-cmu so, what is the solution? Etcd listens neither 4001 nor 7001 port. |
Worth updating the README.md? Was following the tutorial in that and quite baffled that etcd was coming up on port 8080 but not 4001/7001. |
I've made some tweaks to the README to reflect that users should use the tagged releases for now. We also have a couple of imminent changes to clarify the port situation: |
Is 0.5 going to change the etcd binary's public interface? Are all the flags going to change? Just trying to understand how much work it's going to be to change our code to support 0.5. |
@onsi Some flags may be changed because it makes user confused easily, but it should be easy to move from 0.4 to 0.5. |
great thanks! On Thu, Sep 11, 2014 at 11:55 AM, Yicheng Qin [email protected]
|
Works on HEAD today -- much more help, perhaps on the side of too verbose/complicated. And running
|
As of e393509
This is blocking all our pipelines that test against HEAD of etcd....
...and seems pretty bad.
The text was updated successfully, but these errors were encountered: