abiosoft / abiosoft/colima

Can't pull images from internal docker registry

Offen
#335 5 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Go
Sterne
30.8k
Forks
613
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

### Describe the Issue

Being on the company VPN I can't pull images from our internal docker registry. It results in the following error:
```
Using default tag: latest
Error response from daemon: Get "http://

/v2/": dial tcp 192.168.5.121:80: connect: no route to host
```

Me and a colleague did some investigation and it seems like the `192.168.5.0` subnet is used internally in QEMU and LIMA, which seem to result in it trying to download an image from inside its own subnet, which is not working.

### Version

#### Colima Version:

```
colima version 0.4.2
git commit: f112f336d05926d62eb6134ee3d00f206560493b

runtime: docker
arch: x86_64
client: v20.10.17
server: v20.10.11
```

#### Lima Version:

```
limactl version 0.11.0
```

#### Qemu Version

```
qemu-img version 7.0.0
Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developers
```

### Operating System

- [x] macOS Intel
- [ ] macOS m1
- [ ] Linux

### To Reproduce

Steps to reproduce the behavior:

1. Have a private registry hosted on the `192.168.5.0` subnet.
2. Try to pull an image using `docker pull `.
3. Get the following error:
* `Using default tag: latest
Error response from daemon: Get "http://

/v2/": dial tcp 192.168.5.121:80: connect: no route to host`

### Expected behavior

I can pull images from our internal docker registry successfully while using our VPN.

### Additional context

Our registry is not served over TLS so I have added it to the `insecure-registries` list in the docker config.

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.