Failed to create pod sandbox

### Description

Unable to create pods after starting due to:
```
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 31s default-scheduler Successfully assigned kube-system/coredns-d76bd69b-ltgbb to colima
Warning FailedCreatePodSandBox 1s kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to get sandbox image "k8s.gcr.io/pause:3.5": failed to pull image "k8s.gcr.io/pause:3.5": failed to pull and unpack image "k8s.gcr.io/pause:3.5": failed to resolve reference "k8s.gcr.io/pause:3.5": failed to do request: Head "https://k8s.gcr.io/v2/pause/manifests/3.5": dial tcp 142.250.157.82:443: i/o timeout
```

but I can pull image by nerdctl:
```
# nerdctl image pull k8s.gcr.io/pause:3.5
k8s.gcr.io/pause:3.5: resolved |++++++++++++++++++++++++++++++++++++++|
index-sha256:1ff6c18fbef2045af6b9c16bf034cc421a29027b800e4f9b68ae9b1cb3e9ae07: done |++++++++++++++++++++++++++++++++++++++|
manifest-sha256:76ca2030ac3433ab5bbcfdea286b0876b129fc276e0f9d2811674141ea7bab6b: done |++++++++++++++++++++++++++++++++++++++|
config-sha256:f7ff3c40426311c68450b0a2fce030935a625cef0e606ff2e6756870f552e760: done |++++++++++++++++++++++++++++++++++++++|
layer-sha256:d14e130d323c0eeb4a20cb497953bbbd9e25bb6185c463adcb0085ed11200f74: done |++++++++++++++++++++++++++++++++++++++|
elapsed: 2.1 s
```

### Version

colima version:
colima version 0.4.4
git commit: 8bb1101a861a8b6d2ef6e16aca97a835f65c4f8f

runtime: containerd
arch: aarch64
client: v0.20.0
server: v1.5.8

kubernetes
Client Version: v1.24.3
Kustomize Version: v4.5.4
Server Version: v1.23.6+k3s1
---
limactl version: 0.11.2
---
qemu-img version: 7.0.0

### Operating System

- [ ] macOS Intel
- [X] macOS M1
- [ ] Linux

### Reproduction Steps

1. colima start -c 4 -m 4 -d 64 --runtime containerd --kubernetes --network-address
2. kubectl -n kube-system describe pods/coredns-xxxxxxxx-xxxxx
3. colima nerdctl image pull k8s.gcr.io/pause:3.5

### Expected behaviour

It seems that k3s does not respect the proxy settings, but nerdctl does.

### Additional context

_No response_