Bug 1331919 - Need to cache registry.access.redhat.com/openshift3/ose-pod in cdk
Summary: Need to cache registry.access.redhat.com/openshift3/ose-pod in cdk
Keywords:
Status: NEW
Alias: None
Product: Container Development Kit (CDK)
Classification: Red Hat
Component: distribution
Version: 2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta4
: 2.0
Assignee: Lalatendu Mohanty
QA Contact: David Kutálek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-30 03:00 UTC by Dusty Mabe
Modified: 2023-07-21 23:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dusty Mabe 2016-04-30 03:00:22 UTC
Description of problem:

the ose-pod image isn't cached in the cdk which means a user can't bring up openshift when they don't have a network connection


If you do something like run `oc --config /var/lib/openshift/openshift.local.config/master/openshift-master.kubeconfig describe pod router-1-deploy` you will see that it is stuck trying to pull this image:


```
pulling image "openshift3/ose-pod:v3.1.1.6"
  19m           2m              8       {kubelet rhel-cdk}      implicitly required container POD       Failed          Failed to pull image "openshift3/ose-pod:v3.1.1.6": Error while pulling image: Get https://index.docker.io/v1/repositories/openshift3/ose-pod/images: dial tcp: lookup index.docker.io: Temporary failure in name resolution
```


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

$ sha256sum rhel-cdk-kubernetes-7.2-23.x86_64.vagrant-libvirt.box 
70342fe0e3d40265a791e5c61dd6ddba8ce368b5b1f4fa8daf3939e8c585f1f4  rhel-cdk-kubernetes-7.2-23.x86_64.vagrant-libvirt.box


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