Etcd: Procfile Issue when running Goreman after "Getting started" in README

Created on 3 Nov 2019  路  4Comments  路  Source: etcd-io/etcd

Found an issue with the Procfiles used after setting up etcd in the Getting started section.

After moving the release to /usr/local/bin as indicated in the command below:

mv /tmp/etcd-download-test/etcd /usr/local/bin/

Which successfully adds etcd to bin so that we can run etcd via the command line. Now, there comes an issue with Goreman not initiating the etcd cluster as the Procfile indicates /bin/etcd and not /usr/local/bin (as indicated here) The following error then gets logged out:

19:26:46 etcd1 | /bin/sh: 1: bin/etcd: not found

The same happens for Procfile.learner also. A solution I have found is to then modify the Procfile & Procfile.learner by replacing /bin/etcd to /usr/local/bin/etcd

Is this modification alright to get Goreman running easily or is there a possibility that the path to where the etcd release gets moved to gets changed from /usr/local/bin to /bin?

aredoc arequestion

Most helpful comment

They are example files. Please feel free to customize them based on where the etcd binary is located.

All 4 comments

They are example files. Please feel free to customize them based on where the etcd binary is located.

Current instructions seems using master branch. If you are thinking to modify instruction with a PR, I think it's good enough to leave instructions as such and add a comment in both files that use etcd binary location of your env as @jingyih mentioned.

Thanks for reaching out.

Yes, this is true. Indicating to change the etcd location in the Procfiles if it is not in /bin/etcd as comments is a good option. Can I add comments into Procfile & Procfile.learner indicating the above and create a PR?

Sure, that sounds good. Thank you!

Was this page helpful?
0 / 5 - 0 ratings