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

Proxy settings don't propagate to Buildkit #2033

Open
jandubois opened this issue Apr 14, 2022 · 2 comments
Open

Proxy settings don't propagate to Buildkit #2033

jandubois opened this issue Apr 14, 2022 · 2 comments
Assignees
Labels
component/lima Issues related to lima and qemu kind/bug Something isn't working
Milestone

Comments

@jandubois
Copy link
Member

Reported on User Slack:

A friend of mine says he resolved that in 1.2.1 by supplying http proxy env variables to buildkitd tool as they are not propagating from override.yaml

@jandubois jandubois added kind/bug Something isn't working component/lima Issues related to lima and qemu labels Apr 14, 2022
@drcvetkovic
Copy link

Being in corporate environment, we need to set proxies in override.yaml file of lima in _config directory, but it appears that setting is not propagated to buildkit process.

Adding them manually to /etc/init.d/buildkitd seem to fix the issue, but that setting is lost every time rancher desktop is restarted or lima VM is rebooted.

Rancher Desktop 1.2.1, MacOS 12.3.1 Monterey, x86 platform. Various k8s versions.

@jandubois jandubois added this to the Next milestone Apr 14, 2022
@gaktive gaktive modified the milestones: Next, Later Apr 19, 2022
@gaktive gaktive modified the milestones: Next, Later May 17, 2022
@jandubois jandubois self-assigned this Jun 15, 2022
@rumstead
Copy link
Contributor

rumstead commented Jun 17, 2022

Being in corporate environment, we need to set proxies in override.yaml file of lima in _config directory, but it appears that setting is not propagated to buildkit process.

Adding them manually to /etc/init.d/buildkitd seem to fix the issue, but that setting is lost every time rancher desktop is restarted or lima VM is rebooted.

Rancher Desktop 1.2.1, MacOS 12.3.1 Monterey, x86 platform. Various k8s versions.

@drcvetkovic can you share how you added them to buildkit? Just set them as env variables via export?

EDIT: Export works.
#897 (comment)

@jandubois jandubois modified the milestones: Next, Later Jul 14, 2022
@gaktive gaktive modified the milestones: Next, Later Sep 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/lima Issues related to lima and qemu kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants