Starting for the first time behind a corporate proxy stopped working after 0.10.0

[Matthew-hopkins-work]

Description

No response

Version

As of 0.10.0 the mechanism for fetching objects on "colima start" the mechanism for http used the native go http library. Before this colima deferred to "curl".

This causes issues as it was possible to use say a .curlrc file to setup auth against corporate proxies. Especially ones that use SSPI (i.e passing --proxy-negotiate to curl)

Would it be possible to restore the option to use curl for the object download?

Operating System

• macOS Intel <= 13 (Ventura)
• macOS Intel >= 14 (Sonoma)
• Apple Silicon <= 13 (Ventura)
• Apple Silicon >= 14 (Sonoma)
• Linux

Output of colima status

No response

Reproduction Steps

Expected behaviour

No response

Additional context

No response

[abiosoft]

The current implementation allowed Colima to provide a better user experience and remove the external dependency on curl.
However, I can consider providing an option to utilise curl for downloads. Nonetheless It would not be reinstated as the default.

[Matthew-hopkins-work]

The current implementation allowed Colima to provide a better user experience and remove the external dependency on curl. However, I can consider providing an option to utilise curl for downloads. Nonetheless It would not be reinstated as the default.

Having it as something to enable would be greatly appreciated. Digging around adding support for arbitrary proxy auth mechanisms in go would be painful.

I do see there is a --disk-image option too as we could use curl to fetch the image locally first then point it?

Though having optional curl support direct from colima is naturally easier usage wise

[abiosoft]

It would be included in the next release. You can however test with the development version brew install --head colima befoer then.

# use curl via flag
colima start --downloader=curl

# use curl via environment variable
COLIMA_DOWNLOADER=curl colima start