You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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?
Reported on User Slack:
The text was updated successfully, but these errors were encountered: