Skip to content

Please do not check gcr.io, we can not access the gcr.io #26873

Closed
@ghost

Description

8m      8m      1   {default-scheduler }            Normal      Scheduled   Successfully assigned my-nginx-3800858182-hud7j to w
  6m        1m      10  {kubelet w}             Warning     FailedSync  Error syncing pod, skipping: failed to "StartContainer" for "POD" with ImagePullBackOff: "Back-off pulling image \"gcr.io/google_containers/pause:2.0\""

  7m    59s 5   {kubelet w}     Warning FailedSync  Error syncing pod, skipping: failed to "StartContainer" for "POD" with ErrImagePull: "image pull failed for gcr.io/google_containers/pause:2.0, this may be because there are no credentials on this request.  details: (API error (500): Get https://gcr.io/v1/_ping: dial tcp 64.233.189.82:443: i/o timeout\n)"

Activity

dims

dims commented on Jun 6, 2016

@dims
Member

@netroby Looks like you saw a work around in #6888 (comment) is that enough for now?

yujuhong

yujuhong commented on Jun 6, 2016

@yujuhong
Contributor

@netroby, like @dims said, you can specify a different infra container image through --pod-infra-container-image to use whatever image you'd like.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @dims@yujuhong

        Issue actions

          Please do not check gcr.io, we can not access the gcr.io · Issue #26873 · kubernetes/kubernetes