Ben Moss

https://github.com/benmoss/pack/compare/main...no-localhost-proxying fixes the problem for me, but not sure it's how it should really be fixed

@jjbustamante then I can't access other machines on my VPN. I rely on the `PROXY` env variables to tell tools to connect over a proxy, but for Docker those settings...

Maybe there isn't a universal solution to this, what works for me may break someone else's workflow.

I had to run `sudo ln -sf $HOME/.colima/default/docker.sock /var/run/docker.sock` as a workaround, the simpler `export DOCKER_HOST="unix://${HOME}/.colima/default/docker.sock"` did not work for some reason either (that might be a separate bug!)

@mdelapenya looks like it's still a problem with v0.23.0: ``` $ go test ./ 2023/09/08 13:05:53 failed getting information about docker server: Cannot connect to the Docker daemon at unix:///var/run/docker.sock....

On https://github.com/testcontainers/testcontainers-go/commit/69b9fc4405a7e8763081def85102e2a695a06c1d it's even worse: ``` fatal error: sync: unlock of unlocked mutex goroutine 35 [running]: sync.fatal({0x104cd61e0?, 0x0?}) /Users/mossity/sdk/go1.21.0/src/runtime/panic.go:1061 +0x20 sync.(*Mutex).unlockSlow(0x105276e64, 0xffffffff) /Users/mossity/sdk/go1.21.0/src/sync/mutex.go:229 +0x38 sync.(*Mutex).Unlock(0x0?) /Users/mossity/sdk/go1.21.0/src/sync/mutex.go:223 +0x58 sync.(*Once).doSlow(0x8?, 0x105242260?) /Users/mossity/sdk/go1.21.0/src/sync/once.go:76...

It looks like the `docker context` logic lives exclusively in https://github.com/docker/cli, not https://github.com/docker/docker, so unfortunately not very easy to just support contexts directly. It seems like fixing the docs to...

As a workaround I came up with this: ```go t.Cleanup(func() { ctx := context.Background() for _, service := range compose.Services() { container, err := compose.ServiceContainer(ctx, service) if err != nil...