RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1496630 - kube 1.8 fails pulling docker.io image with projectatomic/docker based docker
Summary: kube 1.8 fails pulling docker.io image with projectatomic/docker based docker
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Antonio Murdaca
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-28 00:59 UTC by Seth Jennings
Modified: 2020-06-09 21:28 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-09 21:28:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Seth Jennings 2017-09-28 00:59:52 UTC
Description of problem:

https://github.com/kubernetes/kubernetes/issues/52110

in particular

https://github.com/kubernetes/kubernetes/issues/52110#issuecomment-332674674

When using kube 1.8 (pre-release at this time), the kubelet gets a ErrImagePull when pulling images from the docker hub

Version-Release number of selected component (if applicable):

docker-1.12.6-55

How reproducible:

Always

Steps to Reproduce:
1. clone kubernetes
2. checkout release-1.8
3. hack/local-up-cluster.sh
4. create a simple busybox pod (see yaml below)

Actual results:

kubelet fails to start pod with ErrImagePull

Expected results:

kubelet pulls image successfully and starts pod

Additional info:

pod yaml:

apiVersion: v1
kind: Pod
metadata:
  name: busybox
spec:
  containers:
  - name: busybox
    image: busybox
    command:
    - sleep
    - "3600"
  terminationGracePeriodSeconds: 0
  restartPolicy: Never

Kubernetes has put in a workaround (https://github.com/kubernetes/kubernetes/pull/53161) for EL distros using projectatomic/docker, but we should fix this.

Comment 6 Tom Sweeney 2020-06-09 21:28:11 UTC
We have no plans to ship another version of Docker at this time. RHEL7 is in final support stages where only security fixes will get released.  Customers should move to use Podman which is available starting in RHEL 7.6.


Note You need to log in before you can comment on or make changes to this bug.