[Bug]: GET command fails with i/o timeout

### I have done the following

- [x] I have searched the existing issues
- [ ] If possible, I've reproduced the issue using the 'main' branch of this project

### Steps to reproduce

We are trying to use container as our dev containers. since I wasn't able to use the vscode natively with _container_, I tried building our dockerfile manually with _container_ CLI so that I can later mount vscode to it.
The dockerfile is based on `ubuntu:22.04,` and among other things it tries to download a local version of maven that we saved on an internal server within our VPN.
The command is:
`ADD http:///apache-maven-${MAVEN_VERSION}-bin.tar.gz /destination`

This command results with:
```
------
Error: unknown (2): failed to solve: failed to load cache key: Get "http:///apache-maven-3.9.11-bin.tar.gz": dial tcp :8080: i/o timeout

```
When trying to build the Dockerfile with docker desktop. an image is created with no issues (as mentioned, this is the docker file used for our dev container, so it is being used on a daily basis)
for reference here is the docker command I used to compare :
`docker build -f .devcontainer/DockerFile . `
and here is the _container_ command I used:
`container build -f .devcontainer/DockerFile .`

### Current behavior

The Get command timeouts

### Expected behavior

The get command succeeds

### Environment

```markdown
- OS: macOS 26.0 (25A354)
- Xcode: N/A
- Container: 0.4.1 (build: release, commit: 4ac18b5)
```

### Relevant log output

```shell
=> CANCELED [linux/arm64/v8 4/49] ADD https://download.java.net/java/GA/jdk17.0.2/dfd4a8d0985749f896bed50d7138ee7f/8/ 30.0s
=> CANCELED [linux/arm64/v8 3/49] ADD https://download.java.net/java/GA/jdk17.0.2/dfd4a8d0985749f896bed50d7138ee7f/8/ 30.0s
------
> [linux/arm64/v8 10/49] ADD http:///apache-maven-3.9.11-bin.tar.gz /tmp_downloads:
------
Error: unknown (2): failed to solve: failed to load cache key: Get "http:///apache-maven-3.9.11-bin.tar.gz": dial tcp : i/o timeout
```

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Start by reproducing the issue with .devcontainer/DockerFile using the reported `container build` command, then compare it with `docker build`. Investigate why the GET to the internal Maven URL times out in Container while Docker succeeds; done means the Dockerfile build can retrieve the internal archive successfully.

Written by the indexing model from the issue text.