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

not being able to pull newest 10.1.0.Final tag #55

Open
reegnz opened this issue Jun 16, 2017 · 0 comments
Open

not being able to pull newest 10.1.0.Final tag #55

reegnz opened this issue Jun 16, 2017 · 0 comments

Comments

@reegnz
Copy link

reegnz commented Jun 16, 2017

When I execute docker pull wildfly:10.1.0.Final, I get a docker image from 3 months ago:

 ~ docker images | grep wildfly | grep 10.1.0.Final
jboss/wildfly                                               10.1.0.Final        ab149aa45b9f        3 months ago        584 MB
 ~ docker pull jboss/wildfly:10.1.0.Final
10.1.0.Final: Pulling from jboss/wildfly
Digest: sha256:2b39a89c16854b12706988b8dd959e7873241b8bbaf4e489abe59c69050a7656
Status: Image is up to date for jboss/wildfly:10.1.0.Final

Checking the build logs, it is indeed an image that was built 3 months ago:
https://hub.docker.com/r/jboss/wildfly/builds/bnir2pcakvwa9qsguypj59g/

Successfully built ab149aa45b9f

Pushing index.docker.io/jboss/wildfly:10.1.0.Final...
Done!
Build finished

However the latest build hints at the latest version having a different hash:
https://hub.docker.com/r/jboss/wildfly/builds/bvjraxtuzpj4hsd2wzwrca7/

Successfully built 6b55314cbdf8

Pushing index.docker.io/jboss/wildfly:10.1.0.Final...
Done!
Build finished

This shows, there is either some issue with images on docker.io, but could be my host as well, not sure.

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

1 participant