Skip to content
This repository has been archived by the owner on Feb 24, 2020. It is now read-only.

rkt cannot retrieve containers from Google's container hosting service #726

Closed
brianredbeard opened this issue Apr 3, 2015 · 6 comments
Closed

rkt cannot retrieve containers from Google's container hosting service #726

brianredbeard opened this issue Apr 3, 2015 · 6 comments
Assignees
@iaguis

Comments

@brianredbeard
Copy link
Contributor

In attempting to pull the container located at https://gcr.io/google_containers/kibana:1.2 rkt fails with a 404 error, failing to recognize that the endpoint is a docker registry.

[bharrington@leviathan rkt-v0.5.3]$ curl http://gcr.io/google_containers/kibana:1.2
<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>301 Moved</TITLE></HEAD><BODY>
<H1>301 Moved</H1>
The document has moved
<A HREF="https://gcr.io/google_containers/kibana:1.2">here</A>.
</BODY></HTML>
[bharrington@leviathan rkt-v0.5.3]$ curl https://gcr.io/google_containers/kibana:1.2
<!DOCTYPE html>
<html lang=en>
  <meta charset=utf-8>
  <meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width">
  <title>Error 404 (Not Found)!!1</title>
  <style>
    *{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/errors/logo_sm_2.png) no-repeat}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/errors/logo_sm_2_hr.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/errors/logo_sm_2_hr.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/errors/logo_sm_2_hr.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:55px;width:150px}
  </style>
  <a href=//www.google.com/><span id=logo aria-label=Google></span></a>
  <p><b>404.</b> <ins>That’s an error.</ins>
  <p>The requested URL <code>/google_containers/kibana:1.2</code> was not found on this server.  <ins>That’s all we know.</ins>
[bharrington@leviathan rkt-v0.5.3]$ docker pull gcr.io/google_containers/kibana:1.2
Pulling repository gcr.io/google_containers/kibana
46724d0d1108: Pulling dependent layers 
511136ea3c5a: Download complete 
fa4fd76b09ce: Downloading [==================================================>] 66.26 MB/66.26 MB
^C
[bharrington@leviathan rkt-v0.5.3]$ sudo ./rkt  --insecure-skip-verify run  https://gcr.io/google_containers/kibana:1.2
rkt: fetching image from https://gcr.io/google_containers/kibana:1.2
rkt: warning: signature verification has been disabled
error downloading ACI: bad HTTP status code: 404
[bharrington@leviathan rkt-v0.5.3]$ curl -I https://gcr.io/google_containers/kibana:1.2
HTTP/1.1 404 Not Found
Date: Fri, 03 Apr 2015 22:57:31 GMT
Content-Type: text/html; charset=UTF-8
Server: Docker Registry
Content-Length: 1453
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
Alternate-Protocol: 443:quic,p=0.5
@jonboulle
Copy link
Contributor

@brianredbeard two things:

  1. the correct syntax for Docker repositories is prefixed with the docker:// scheme:
# rkt  --insecure-skip-verify run docker://gcr.io/google_containers/kibana:1.2
rkt: fetching image from docker://gcr.io/google_containers/kibana:1.2
error converting docker image to ACI: error getting ImageID from tag 1.2: HTTP code: 405. URL: https://gcr.io/v1/repositories/google_containers/kibana/tags/1.2

This is documented here but if you have suggestions for making it clearer elsewhere I'd gladly accept a PR.

  1. It seems like gcr.io doesn't properly implement the Docker registry API? Hence the command above failing - the tags endpoints (e.g. https://gcr.io/v1/repositories/google_containers/kibana/tags, https://gcr.io/v1/repositories/google_containers/kibana/tags/1.2) are 405ing for no good reason I can tell...

@jonboulle
Copy link
Contributor

/cc @iaguis

@jonboulle jonboulle mentioned this issue Apr 8, 2015
Closed
@jonboulle
Copy link
Contributor

This should be fixed upstream in appc/docker2aci#39

@jonboulle
Copy link
Contributor

@iaguis would you mind bumping docker2aci for this?

@iaguis
Copy link
Member

iaguis commented Apr 13, 2015

Sure #757

@jonboulle
Copy link
Contributor

Fixed on master:

core@core-01 ~ $ sudo rkt/bin/rkt  --insecure-skip-verify run docker://gcr.io/google_containers/kibana:1.2rkt: fetching image from docker://gcr.io/google_containers/kibana:1.2
Downloading layer: 511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158
Downloading layer: fa4fd76b09ce9b87bfdc96515f9a5dd5121c01cc996cf5379050d8e13d4a864b
Downloading layer: 1c8294cc516082dfbb731f062806b76b82679ce38864dd87635f08869c993e45
Downloading layer: 117ee323aaa9d1b136ea55e4421f4ce413dfc6c0cc6b2186dea6c88d93e1ad7c
Downloading layer: 2d24f826cb16146e2016ff349a8a33ed5830f3b938d45c0f82943f4ab8c097e7
Downloading layer: b0ea89e782846f154bb66320a9a77a78c2034073c2a5ddd7b2e764583331893d
Downloading layer: 766170f46862db046c7bf82fa5bf4492596c498dd1586b04aea6264313ce480a
Downloading layer: fcee129da010870aa8e75d05df00182ab060c6aa23dd1e214cea44c2baaae5aa
Downloading layer: 9a5a23ed0555e7d578fbb40e712798d986cf3edfb5dc03d97d3bf252a196528a
Downloading layer: e0aaabb71767668df3599627f309af343fb8cdd0e64aed28458713132810d16e
Downloading layer: dea2d196e2a85a2d49ebcad3afce28e2729785c147f219816cc250fac07f39cd
Downloading layer: 7f0261c5e5515aebf8903440b3670f15b53da7ab6e62428cf8f8dc76c487e4ac
Downloading layer: 46724d0d11088322e3a9e7a93ffbb5f3ca1854fa845f7ed62d217d994917aebc
Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining processes...
Unmounting file systems.
Unmounting /opt/stage2/sha512-d4f266ce10f653674ca1b0eb5252222a/rootfs/dev/pts.
Unmounting /opt/stage2/sha512-d4f266ce10f653674ca1b0eb5252222a/rootfs/dev/shm.
Unmounting /opt/stage2/sha512-d4f266ce10f653674ca1b0eb5252222a/rootfs/sys.
Unmounting /opt/stage2/sha512-d4f266ce10f653674ca1b0eb5252222a/rootfs/proc.
Unmounting /opt/stage2/sha512-d4f266ce10f653674ca1b0eb5252222a/rootfs/dev/console.
Unmounting /opt/stage2/sha512-d4f266ce10f653674ca1b0eb5252222a/rootfs/dev/tty.
Unmounting /opt/stage2/sha512-d4f266ce10f653674ca1b0eb5252222a/rootfs/dev/urandom.
Unmounting /opt/stage2/sha512-d4f266ce10f653674ca1b0eb5252222a/rootfs/dev/random.
Unmounting /opt/stage2/sha512-d4f266ce10f653674ca1b0eb5252222a/rootfs/dev/full.
Unmounting /opt/stage2/sha512-d4f266ce10f653674ca1b0eb5252222a/rootfs/dev/zero.
Unmounting /opt/stage2/sha512-d4f266ce10f653674ca1b0eb5252222a/rootfs/dev/null.
Unmounting /opt/stage2/sha512-d4f266ce10f653674ca1b0eb5252222a/rootfs.
Unmounting /proc/sys/kernel/random/boot_id.
Unmounting /opt/stage2/sha512-d4f266ce10f653674ca1b0eb5252222a/rootfs.
All filesystems unmounted.
Halting system.

Mind you I have no idea how to actually use this container (docker run also exits immediately), but @brianredbeard if you have further issues please file another report.

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

@iaguis iaguis

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@brianredbeard @iaguis @jonboulle