相关问题
- WebSockets on OpenShift do not work with remote cl
- “oc new-app” does not expose port altough the inpu
- rhc setup returns “warning: constant ::TimeoutErro
- Kubernetes - Readiness Probe execution after conta
- Validate OpenShift objects defined in yaml before
相关文章
- How to obtain the enable admission controller list
- Difference between API versions v2beta1 and v2beta
- Git Pull from Openshift using Windows: Invalid ref
- openshift with nodejs isn't respecting the pat
- How to allow image pull from one project to anothe
- Deploy a Grails 2.1.1 application to Tomcat as an
- How to cleanup disk space on openshift when 'r
- Testing spring openshift application locally
You can apply a workaround for this issue by removing Image Change Trigger and removing the hash from
image
attribute in container spec.Modify the build config:
Replace to:
Unfortunately this is a side-effect of DockerHub removing backwards compatibility for Docker 1.9 daemons. When images are pushed using Docker 1.10, pull-by-id will fail for older daemons (which includes OpenShift masters importing metadata from the Hub). You can work around this by pulling the centos image and pushing it to the internal registry.
At the current time, using Docker 1.9 on your hosts will avoid this issue.