-
Notifications
You must be signed in to change notification settings - Fork 38
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
ETCD_PEER does not respect port #29
Comments
try ETCD_PEER=http://a.b.c.d:2379 format. |
Thanks, I will try it now. Definitely should update the README.md under the "Getting Started" section |
Nope. Then it adds the port and prepends http:// Debug output My launch command:
|
The current source has fixed the bug but it is not in the current purpleworks/fleet-ui:latest image (165d50cf624b). |
That would explain it. I will use the workaround for now. Any plans to push the fix to |
@deitch you can pull the new image with the port fixes here: https://hub.docker.com/r/dockerage/fleet-ui/
|
Excellent. I will use that. Is that the new official image? Or just a temporary fork? |
It's a temp fork. I don't own the official one. |
Got it. Thanks @xuwang . I will leave this open until @purpleworks updates the image. |
finally, update image. Thank you. |
Thanks @subicura |
I am running etcd 2.x, so the official IANA port of 2379 is in use. When I run fleet-ui, I pass it the
-e ETCD_PEER=a.b.c.d:2379
option.However, if I
exec
into the running container and stub/usr/local/bin/fleetctl
, I see that it tries to send itfleetctl --endpoint http://172.30.20.160:2379:4001
(notice the appended:4001
).Ran purpleworks/fleet-ui:latest, image id is 165d50cf624b
The text was updated successfully, but these errors were encountered: