Skip to content

Receive error code 502 when pushing images to container registry through a proxy #12832

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

Closed
Tracked by #12825
mrsimonemms opened this issue Sep 9, 2022 · 3 comments
Closed
Tracked by #12825
Labels
meta: never-stale This issue can never become stale

Comments

@mrsimonemms
Copy link
Contributor

mrsimonemms commented Sep 9, 2022

During the investigations of #10769, I made a simple version of #12829 by hardcoding all the envvars into an image. This gave a series of 502 errors when pushing images to my container registry.

Once the work for #12829 has been done, this will be the next thing to do.

NB this ticket is more an aide-mémoire that a problem potentially exists rather than an expectation of some work to be done

@kylos101 kylos101 changed the title Investigate build errors 502 errors when pushing images to container registry through a proxy Sep 9, 2022
@kylos101 kylos101 changed the title 502 errors when pushing images to container registry through a proxy Receive error code 502 when pushing images to container registry through a proxy Sep 9, 2022
@kylos101
Copy link
Contributor

kylos101 commented Sep 9, 2022

@mrsimonemms does this issue rename align with the problem you were experiencing?

@mrsimonemms
Copy link
Contributor Author

Sure. It's perfectly plausible that this issue goes away when #12829 is done, so this issue shouldn't be worked on until that other issue is done

@stale
Copy link

stale bot commented Dec 16, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Dec 16, 2022
@mrsimonemms mrsimonemms added meta: never-stale This issue can never become stale and removed meta: stale This issue/PR is stale and will be closed soon labels Jan 21, 2023
@mrsimonemms mrsimonemms closed this as not planned Won't fix, can't repro, duplicate, stale Jun 27, 2023
@github-project-automation github-project-automation bot moved this to Awaiting Deployment in 🌌 Workspace Team Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta: never-stale This issue can never become stale
Projects
No open projects
Status: Awaiting Deployment
Development

No branches or pull requests

2 participants