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

add registry.relativeurls value #271

Merged
merged 1 commit into from Sep 18, 2019
Merged

add registry.relativeurls value #271

merged 1 commit into from Sep 18, 2019

Conversation

pablo-ruth
Copy link
Contributor

Add a value to config relativeurls support on registry. This is needed when expose.type is not set to ingress to avoid "unkown blob" error on image push.

Resolves #174

@pablo-ruth pablo-ruth changed the title add registry.relativeurl value add registry.relativeurls value Jun 27, 2019
@BartJoris
Copy link

Hi, any updates on this?

@deschmih
Copy link

I need this too, because same error occurs when running the registry on non default port. So this fix would help.

@ywk253100
Copy link
Collaborator

@pablo-ruth Could you resolve the conflict?

values.yaml Outdated Show resolved Hide resolved
@pablo-ruth
Copy link
Contributor Author

Ok done :)

@ywk253100
Copy link
Collaborator

@pablo-ruth Could you squash all commits into a single one?

Signed-off-by: Pablo RUTH <contact@pablo-ruth.fr>
@pablo-ruth
Copy link
Contributor Author

Done, commits are squashed

@ywk253100
Copy link
Collaborator

@pablo-ruth Thanks!

@ywk253100 ywk253100 merged commit 85d446f into goharbor:master Sep 18, 2019
@problame
Copy link

problame commented Jun 3, 2020

ISTM that this needs to be back-ported to the component that generates docker-compose.yml.

ref #174 (comment)

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

Successfully merging this pull request may close these issues.

"unknown blob" error while pushing images to harbor
5 participants