Skip to content
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

Docker Hub failed to build consul-server and consul-agent against 0.6.4 #135

Closed
ushuz opened this issue Apr 10, 2016 · 4 comments
Closed

Comments

@ushuz
Copy link

ushuz commented Apr 10, 2016

Pull the latest image of consul-server and consul-agent from Docker Hub, then run:

$ docker run -d --name consul-server gliderlabs/consul-server:latest
$ docker exec consul-server /bin/consul version
Consul v0.6.3
Consul Protocol: 3 (Understands back to: 1)
$ docker run -d --name consul-agent gliderlabs/consul-agent:latest
$ docker exec consul-agent /bin/consul version
Consul v0.6.3
Consul Protocol: 3 (Understands back to: 1)
@CpuID
Copy link

CpuID commented Apr 13, 2016

Definitely would be nice to have resolved. Are we able to get x.y.z tags on Docker Hub? As opposed to just x.y?

@mistaka0s
Copy link

Looks like the gliderlabs/consul docker image failed to build and it used the older version of the container to build consul-server and consul-agent using 0.6.3.

Are you able to kick off a rebuild?
https://hub.docker.com/r/gliderlabs/consul/builds/buuyepcuwhatskhhbvnwgmc/

@ianmcorvidae
Copy link

New builds have evidently been triggered and consul-server and consul-agent now both report 0.6.4. I believe this is resolved.

@ushuz
Copy link
Author

ushuz commented Apr 23, 2016

@ianmcorvidae Indeed, the problem is resolved. I'm closing this issue.

@ushuz ushuz closed this as completed Apr 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants