-
Notifications
You must be signed in to change notification settings - Fork 880
Missing scope in bearer auth challenge when fetching from private quay.io repository #2248
Comments
Yup, I can reproduce this. I'll see if I can come up with a fix. Sorry about that. |
No worries, thanks for your help! :) |
And here's the fix: appc/docker2aci#126. Once that gets merged I'll make a PR against rkt to bump the version of docker2aci it uses. |
Sounds good, thanks again! On Sat, Mar 5, 2016 at 11:07 AM, Derek Gonyeo notifications@github.com
|
Cool, looks like appc/docker2aci#126 was merged. Any chance you could bump the version in rkt now? I'd be glad to test the fix. :) |
Sorry, didn't mean to click "close" quite yet... :P |
I'll try to put together the PR for rkt to bump docker2aci tomorrow, unless someone else wants to beat me to it.
|
Cool, just created #2267. I verified that it works for me (I can pull from my private quay.io account now). |
Thanks, sorry about me being slow in getting around to that. On Wed, Mar 9, 2016 at 5:54 PM, Brett Bethke notifications@github.com
|
No problem! Haha, I was excited to test it so I figured I'd go ahead. Thanks for fixing the root issue in |
This pulls in the latest docker2aci. Fixes rkt#2248.
I'm trying to use rkt to pull a docker image from a private quay.io repository. I've set up my credentials according to the instructions here. My
/etc/rkt/auth.d/quay.json
file looks like this:However, when I do
# rkt fetch --insecure-options=image docker://quay.io/my_organization/my_image:tag
I get this error:
fetch: missing scope in bearer auth challenge
. Any ideas what might be wrong? Thanks!The text was updated successfully, but these errors were encountered: