search

abiosoft / colima

Container runtimes on macOS (and Linux) with minimal setup
MIT License
19.68k stars 397 forks source link

Colima doesn't work with VPN resolution #88

Open kevdowney opened 2 years ago

kevdowney commented 2 years ago

When connected to an enterprise VPN docker cannot resolve internal hostnames for registry.

 => ERROR [internal] load metadata for docker.corp.com/docker-rmt/ubuntu:latest                                                                                                    20.0s
------
 > [internal] load metadata for docker.corp.com/docker-rmt/golang:1.16:
------
------
 > [internal] load metadata for docker.corp.com/docker-rmt/ubuntu:latest:
------
failed to solve with frontend dockerfile.v0: failed to create LLB definition: failed to do request: Head https://docker.corp.com/v2/docker-rmt/ubuntu/manifests/latest: dial tcp: lookup docker.corp.com: Temporary failure in name resolution
make: *** [docker-build] Error 1

Docker Version:

docker version
Client: Docker Engine - Community
 Version:           20.10.11
 API version:       1.41
 Go version:        go1.17.2
 Git commit:        dea9396e18
 Built:             Wed Nov 17 23:49:46 2021
 OS/Arch:           darwin/amd64
 Context:           default
 Experimental:      true

Server:
 Engine:
  Version:          20.10.7
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.8
  Git commit:       20.10.7-0ubuntu5.1
  Built:            Thu Oct 21 23:58:58 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.5.5-0ubuntu3
  GitCommit:
 runc:
  Version:          1.0.1-0ubuntu2
  GitCommit:
 docker-init:
  Version:          0.19.0
  GitCommit:

Colima version:

colima version
colima version 0.2.2
git commit: b2c7697bee2d73e995f156fe8e9870eb246c07e6

runtime: docker
client: v20.10.11
server: v20.10.7
abiosoft commented 2 years ago

Kindly install latest development version with brew install --head colima, then colima delete and start afresh.

slimm609 commented 2 years ago

had a similar issue and tried the head version and now no containers can get DNS

# dig www.google.com
; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.amzn2.5.2 <<>> google.com
;; global options: +cmd
;; connection timed out; no servers could be reached
deviantintegral commented 2 years ago

This appears to have regressed in HEAD. In 0.3.4 I can successfully connect to hosts over an OpenVPN connection. In HEAD, while DNS resolves fine all connections time out.

boardwalk commented 2 years ago

Can confirm deviantintegral’s issue. When connected to a VPN (GlobalProtect in my case), DNS works but no connections do. Reverted to 0.3.4 and now things are working.

MShekow commented 1 year ago

Problem exists in 0.6.5 again. DNS resolution is not the issue, the connection simply cannot be established. With Docker Desktop it works fine.