abiosoft / abiosoft/colima

Colima, buildx and docker daemon setup

Aperta
#1,309 8 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Go
Stelle
30.8k
Fork
613
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

Hello everyone, this is probably more of a "how to configure Colima properly" rather than an actual issue or maybe it's an issue I am not sure, it is sort of subjective on this one I would say.

Like many people I made the switch to Colima from Docker Desktop and love Colima to pieces but, there is a little thing that is really driving me nuts and I am not sure how to go about it so that it works in a seamless way. The problem has to do with how Colima manages docker contexts and buildx contexts, if I run `docker context ls` I get the following:
```shell
~ docker context ls
NAME DESCRIPTION DOCKER ENDPOINT ERROR
colima * colima unix:///Users/marco.debortoli/.colima/default/docker.sock
default Current DOCKER_HOST based configuration unix:///var/run/docker.sock
```
All good, nice and clean as I expect it to be. But when I run `docker buildx ls` I get the following instead:
```shell
docker buildx ls
NAME/NODE DRIVER/ENDPOINT STATUS BUILDKIT PLATFORMS
colima* docker
\_ colima \_ colima running v0.20.0 linux/arm64
default error

Cannot load builder default: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
```
Which again is somehow right because nothing is running on `unix:///var/run/docker.sock` but it is really gets to my head to see that error. I know that a way to make if work is to set the `DOCKER_HOST` variable but if I do that then this is what I get running `docekr context ls` again:
```shell
docker context ls
NAME DESCRIPTION DOCKER ENDPOINT ERROR
colima colima unix:///Users/marco.debortoli/.colima/default/docker.sock
default * Current DOCKER_HOST based configuration unix:///Users/marco.debortoli/.colima/default/docker.sock
Warning: DOCKER_HOST environment variable overrides the active context. To use a context, either set the global --context flag, or unset DOCKER_HOST environment variable.
```
So basically I just move the error to a warning in another place and it also doesn't feel clean/right.

My question then is, what's a clean way to go about this and having Colima work in these scenarios without errors or warning? Thank you for any insight you can provide.

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.