Syft does not use HTTP proxy when downloading the Docker image itself

[gbonnefille]

What happened:

In a corporate network, with a corporate proxy,
When I run syft on a Docker image hosted outside
Then it fails with a message:

failed to construct source from user input "123vlk6z.graX.container-registry.ovh.net/project/component/snapshot": unable to load image: unable to use OciRegistry source: failed to get image descriptor from registry: Get "https://123vlk6z.graX.container-registry.ovh.net/v2/": read tcp 10.42.3.252:40532->123.19.108.56:443: read: connection reset by peer

It is clearly trying to access directly to the external registry, without passing through the proxy (set via https_proxy and HTTPS_PROXY).

What you expected to happen:

Syft should respect the HTTP proxy.

Steps to reproduce the issue:

Hard way if outside a corporate network.

Anything else we need to know?:

Environment:

• Output of syft version: 0.92.0
• OS (e.g: cat /etc/os-release or similar): Linux Ubuntu 22.04

[cschelcher]

Hello,
As far as I know, this started with v0.91.0.
v0.90.0 respects proxy settings

[gbonnefille]

Hello, As far as I know, this started with v0.91.0. v0.90.0 respects proxy settings

I'm not sure to understand: do you mean this is a regression? Working on v0.90.0 but not working on v0.91.0?

[cschelcher]

I'm not sure to understand: do you mean this is a regression? Working on v0.90.0 but not working on v0.91.0?

Yes, this is working with v0.90.0.
With v0.91.0+ it times out trying to get the image directly.

[daHaimi]

Just popped into this issue yesterday. Are there any advisories/quick fixes available?

Background: We are trying to run syft behind a corporate proxy inside a container.