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

Docker Registry 2.7.0 panic #1831

Closed
cdalvaro opened this issue Jan 5, 2019 · 6 comments
Closed

Docker Registry 2.7.0 panic #1831

cdalvaro opened this issue Jan 5, 2019 · 6 comments
Labels

Comments

@cdalvaro
Copy link
Contributor

cdalvaro commented Jan 5, 2019

There is a panic issue with Docker Registry latest (current version 2.7.0)

panic: unable to configure authorization (token): token auth requires a valid option bool: autoredirect

For those with this problem, replace in your compose file the registry image from latest to 2.6.2

@cdalvaro
Copy link
Contributor Author

cdalvaro commented Jan 5, 2019

You can use registry:latest if you add the following env variable to your registry environment:

services:
  ...
  registry:
    image: registry:latest
    environment:
      - REGISTRY_AUTH_TOKEN_AUTOREDIRECT=false

At the moment, this is the only 'documentation' I have found: distribution/distribution#2793

Info about the corresponding PR: distribution/distribution#2711

@solidnerd
Copy link
Collaborator

Hey,

it seems that it's a problem from the registry, because 2.7.0 is not semver. It violates it through this setting.

To fix it in your instance you can set the following env:

REGISTRY_AUTH_TOKEN_AUTOREDIRECT=true

or use it in your config.yml:

...
token:
    autoredirect: true    
    service: container_registry   
    issuer: gitlab-issuer
...

@solidnerd
Copy link
Collaborator

Oh you was 19 seconds earlier than my post. But It fixes the problem.

@cdalvaro
Copy link
Contributor Author

cdalvaro commented Jan 5, 2019

Based on what I have read, the value false maintains the old behavior, but I'm not sure about if true is more correct.

@stale
Copy link

stale bot commented May 7, 2020

This issue has been automatically marked as stale because it has not had any activity for the last 60 days. It will be closed if no further activity occurs during the next 7 days. Thank you for your contributions.

@stale stale bot added the wontfix label May 7, 2020
@cdalvaro
Copy link
Contributor Author

Maybe this is not working as expected...

Screen Shot 2020-05-20 at 07 52 41

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

No branches or pull requests

2 participants