Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't export images from a build #2142

Open
jeffmaury opened this issue Mar 16, 2018 · 8 comments
Open

Can't export images from a build #2142

jeffmaury opened this issue Mar 16, 2018 · 8 comments

Comments

@jeffmaury
Copy link

General information

  • Minishift version: v1.14.0+2b3e3a2
  • OS: Windows
  • Hypervisor: VirtualBox

Steps to reproduce

  1. Create a nodejs deployement
  2. Try to export the corresponding builder image

Expected

We should be able to export the image but it has no tag so how to do ?

Actual

Can't export the image

Logs

docker images:

> docker images                                                                                                                                      
time="2018-03-16T17:52:17+01:00" level=info msg="Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows"   
REPOSITORY                                                  TAG                 IMAGE ID            CREATED             SIZE                         
172.30.1.1:5000/node/nodejs-ex                              latest              41c8f036c5aa        8 hours ago         539 MB                       
registry.access.redhat.com/rhscl/nodejs-4-rhel7             <none>              268a36ecd969        2 weeks ago         521 MB                       
registry.access.redhat.com/openshift3/ose-deployer          v3.7.23             e786abbc9e3b        6 weeks ago         1.09 GB                      
registry.access.redhat.com/openshift3/ose-haproxy-router    v3.7.23             de6071d52a3a        8 weeks ago         1.08 GB                      
registry.access.redhat.com/openshift3/ose-sti-builder       v3.7.23             70e583f1af83        8 weeks ago         1.06 GB                      
registry.access.redhat.com/openshift3/ose-docker-registry   v3.7.23             9f5054d95f6b        8 weeks ago         459 MB                       
registry.access.redhat.com/openshift3/ose                   v3.7.23             d14f0a1a4af8        8 weeks ago         1.06 GB                      
registry.access.redhat.com/openshift3/ose-pod               v3.7.23             f9d210d18f78        8 weeks ago         209 MB                       
                                                                                                                                                     

You can start Minishift with minishift start --show-libmachine-logs -v5 to collect logs.
Please consider posting this on http://gist.github.com/ and post the link in the issue.

@anjannath
Copy link
Member

have you tried the minishfit image export command?

@coolbrg
Copy link
Contributor

coolbrg commented Mar 19, 2018

@jeffmaury Could you try

$ minishift image export registry.access.redhat.com/rhscl/nodejs-4-rhel7

# To check the list of exported/cached images
$ minishift image list

@jeffmaury
Copy link
Author

This work for nodejs as the image from the wizard is the same as latest. But not not work for EAP deployments.
See the list of images are the export command:

> docker images                                                                                                                                      
time="2018-03-19T14:06:53+01:00" level=info msg="Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows"   
REPOSITORY                                                  TAG                 IMAGE ID            CREATED             SIZE                         
172.30.1.1:5000/eap/eap-app                                 latest              241df2a7ef5c        3 minutes ago       710 MB                       
172.30.1.1:5000/node1/nodejs-ex                             latest              2bba55b0e21d        14 minutes ago      539 MB                       
172.30.1.1:5000/node/nodejs-ex                              latest              50df7baf29d9        38 minutes ago      506 MB                       
registry.access.redhat.com/rhscl/nodejs-4-rhel7             <none>              268a36ecd969        2 weeks ago         521 MB                       
registry.access.redhat.com/rhscl/nodejs-6-rhel7             latest              b3527e45dfd6        2 weeks ago         490 MB                       
registry.access.redhat.com/jboss-eap-7/eap70-openshift      latest              c79e69ff7150        6 weeks ago         698 MB                       
registry.access.redhat.com/openshift3/ose-deployer          v3.7.23             e786abbc9e3b        6 weeks ago         1.09 GB                      
registry.access.redhat.com/openshift3/ose-haproxy-router    v3.7.23             70528d2c4bb2        2 months ago        1.08 GB                      
registry.access.redhat.com/openshift3/ose-sti-builder       v3.7.23             70e583f1af83        2 months ago        1.06 GB                      
registry.access.redhat.com/openshift3/ose-docker-registry   v3.7.23             137b523d5df3        2 months ago        459 MB                       
registry.access.redhat.com/openshift3/ose                   v3.7.23             72c4f3528bfd        2 months ago        1.06 GB                      
registry.access.redhat.com/openshift3/ose-pod               v3.7.23             f9d210d18f78        2 months ago        209 MB                       
registry.access.redhat.com/jboss-eap-7/eap70-openshift      <none>              4490c33a88d5        3 months ago        698 MB                       

@stale
Copy link

stale bot commented May 18, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status/stale label May 18, 2018
@anjannath
Copy link
Member

anjannath commented May 19, 2018 via email

@stale stale bot removed the status/stale label May 19, 2018
@stale
Copy link

stale bot commented Jul 18, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status/stale label Jul 18, 2018
@jeffmaury
Copy link
Author

Still todo

@stale stale bot removed the status/stale label Jul 19, 2018
@stale
Copy link

stale bot commented Sep 17, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

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

No branches or pull requests

3 participants