Skip to content

Pushes to docker.io are using Pipeline name instead of registry username specified in pipeline settings #634

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

Open
drashy opened this issue Apr 15, 2025 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@drashy
Copy link

drashy commented Apr 15, 2025

When Kubero attempts to push an image to a repo it uses the pipeline-name rather than the pre-configured registry-username so it ends up trying to push to a registry that does not exist and/or it has no access to.

Issue(s) occurs on these line(s) I believe: (of course I could be wrong)

image: process.env.KUBERO_BUILD_REGISTRY + "/" + pipeline + "/" + app,

image: `${process.env.KUBERO_BUILD_REGISTRY}/${pipeline}/${appName}`,

@drashy
Copy link
Author

drashy commented Apr 15, 2025

Also, I question whether it should be using process.env.KUBERO_BUILD_REGISTRY at all, shouldn't this use the registry settings in the pipeline or is the env var populated from the pipeline settings?

@mms-gianni mms-gianni added the bug Something isn't working label Apr 16, 2025
@mms-gianni mms-gianni self-assigned this Apr 16, 2025
@mms-gianni
Copy link
Member

Thank you for raising this bug.

I think i should refactor this in general a bit.

mms-gianni added a commit that referenced this issue Apr 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants