8000 fix panic when using storage redirect middleware by Windfarer · Pull Request #2081 · distribution/distribution · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

fix panic when using storage redirect middleware #2081

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

Merged
merged 1 commit into from
Jan 3, 2017
Merged

fix panic when using storage redirect middleware #2081

merged 1 commit into from
Jan 3, 2017

Conversation

Windfarer
Copy link
Contributor
@Windfarer Windfarer commented Nov 24, 2016

fix panic when using storage redirect middleware in registry version 2.5.1
When we start registry with storage redirect middleware in config file, it will panic. The error message can be show as follows:

unable to configure storage middleware (redirect): no storage middleware registered with name: redirect

this PR fix this problem by importing storage redirect middleware in main.go

Signed-off-by: Eric Yang <windfarer@gmail.com>
@codecov-io
Copy link
codecov-io commented Nov 24, 2016

Current coverage is 52.55% (diff: 100%)

Merging #2081 into release/2.5 will decrease coverage by 10.14%

@@           release/2.5      #2081   diff @@
=============================================
  Files              120        120           
  Lines            10496      10496           
  Methods              0          0           
  Messages             0          0           
  Branches             0          0           
=============================================
- Hits              6581       5516   -1065   
- Misses            3038       4238   +1200   
+ Partials           877        742    -135   

Powered by Codecov. Last update 2c3b616...6c985f7

@dmcgowan
Copy link
Collaborator

We likely are not going to do a 2.5.2 release, the original change can be picked up in 2.6.0-rc1 by using the image registry:2.6.0-rc.1.

@Windfarer
Copy link
Contributor Author

@dmcgowan We cannot run an RC version in production environment. Could you tell me when is the release date of stable 2.6 version? Thanks a lot.

@stevvooe
Copy link
Collaborator

LGTM

@dmcgowan dmcgowan merged commit 6b114e6 into distribution:release/2.5 Jan 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants
0