Bacalhau cannot connect to Docker when socket location is non-standard about bacalhau

[simonwo]

But, why is it Bacalhau cannot resolve this but Docker can?

It's something to do with docker context:

% docker context list
NAME                TYPE                DESCRIPTION                               DOCKER ENDPOINT                               KUBERNETES ENDPOINT   ORCHESTRATOR
default             moby                Current DOCKER_HOST based configuration   unix:///var/run/docker.sock                                         
desktop-linux *     moby                Docker Desktop                            unix:///Users/simon/.docker/run/docker.sock                         

Docker internally seems to be storing contextual informaiton in ~/.docker/config.json and ~/.docker/contexts on at least systems with Docker Desktop (Macs and probably Windows). This looks like a closed-source proprietary addition to Docker and not part of the open-source version Moby.

To fix this issue, we could:

• double-check that there is nowhere open-source that Docker are making available this contexts feature
• if not, write our own parser for the contexts structure into our Docker client (it's not complicated)

% cat config.json
{
	"auths": {
		"ghcr.io": {}
	},
	"credsStore": "desktop",
	"currentContext": "desktop-linux"
}
% cat contexts/meta/fe9c6bd7a66301f49ca9b6a70b217107cd1284598bfc254700c989b916da791e/meta.json 
{"Name":"desktop-linux","Metadata":{"Description":"Docker Desktop"},"Endpoints":{"docker":{"Host":"unix:///Users/simon/.docker/run/docker.sock","SkipTLSVerify":false}}}%

[aronchick]

Taking on more visible errors is super important - we just keep running into this.

I don't want to turn this bug into the feature - created a new one - #3059

[simonwo]

This is still a bug, separate from the error message given.

[wdbaruni]

This is still an issue that I just faced after updating my docker desktop