Change:
// No Tag or SHA specified, so just return what we have return true } if isTagged { <del> hostname, _ := dockerref.SplitHostname(named) // Check the RepoTags for an exact match </del> <ins> // Check the RepoTags for a match. </ins> for _, tag := range inspected.RepoTags { <del> // Deal with image with hostname specified if len(hostname) > 0 { if strings.HasSuffix(image, tag) { return true } } else { if tag == image { // We found a specific tag that we were looking for return true } </del> <ins> // An image name (without the tag/digest) can be [hostname '/'] component ['/' component]* // Because either the RepoTag or the name *may* contain the // hostname or not, we only check for the suffix match. if strings.HasSuffix(image, tag) || strings.HasSuffix(tag, image) { return true </ins> } } } if isDigested { algo := digest.Digest().Algorithm().String() sha := digest.Digest().Hex()

Discussion:
I cannot create pod. shows the following error shows the following message Tracing back to the source, the newly image check function from prints the message
when you run into such issue, have you tried docker pull to see if docker hub is down? Also you are using image kubernetes/pause for testing?
when did you build your cluster? was merged yesterday.
yes, docker pull worked for that image and I compared container id, it matches the sha in the kubelet log. The new fix is not in my tree yet. I'll check it out. Thank you for helping.
still not working console commit Merge: Author: Kubernetes Submit Queue <k8s-merge- Wed Aug 17 00:54:33 2016 -0700 Merge pull request from hodovska/-non-k8scontainers Automatic merge from submit-queue Add note: kubelet manages only k8s containers. Kubelet wrote log when accesing container which was not created in k8s, what could confuse users. That's why we note about it in documentation and lowered log level of the message to 5. Here is example of the message: bug Bugzilla link commit Author: Dominika Hodovska <: Thu Aug 11 10:00:13 2016 +0200 Add note: kubelet manages only k8s containers.

bug Bugzilla link 3m 58s 5 {kubelet rootfs-dev} spec.containers{web} Normal Pulling pulling image "kubernetes/pause" 3m 56s 5 {kubelet rootfs-dev} spec.containers{web} Warning Failed Failed to pull image "kubernetes/pause": image pull failed for unknown error 3m 56s 5 {kubelet rootfs-dev} Warning FailedSync Error syncing pod, skipping: failed to "StartContainer" for "web" with ErrImagePull: "image pull failed for unknown error" 3m 10s 13 {kubelet rootfs-dev} spec.containers{web} Normal BackOff Back-off pulling image "kubernetes/pause" 3m 10s 13 {kubelet rootfs-dev} Warning FailedSync Error syncing pod, skipping: failed to "StartContainer" for "web" with ImagePullBackOff: "Back-off pulling image "kubernetes/pause"" I0817 15:26:14. ] Connecting to docker on I0817 15:26:14. ] Start docker client with request timeout=2m0s I0817 15:30:36. ] Pulling image kubernetes/pause:latest without credentials I0817 15:30:38. ] Inspected image ("c80eebea8921a5e97f82fcf60da84f4de6399b9fc0ba683ceff67cd0dd319644") does not match kubernetes/pause:latest I0817 15:30:52. ] Pulling image kubernetes/pause:latest without credentials I0817 15:30:55. ] Inspected image ("c80eebea8921a5e97f82fcf60da84f4de6399b9fc0ba683ceff67cd0dd319644") does not match kubernetes/pause:latest I0817 15:31:19. ] Pulling image kubernetes/pause:latest without credentials I0817 15:31:21. ]

Inspected image ("c80eebea8921a5e97f82fcf60da84f4de6399b9fc0ba683ceff67cd0dd319644") does not match kubernetes/pause:latest
could you post the output of ?
I use to start my cluster, maybe there is a missing option
Uh...I think this is the opposite case of what PR was fixing. Uploaded to fix this.
Thanks for taking care of this!