Can I customize DOCKER_HOST and DOCKER_CONTEXT?

[Kentzo]

Is it intentional that the extension requires a local docker daemon?

[rcjsuen]

Is it intentional that the extension requires a local docker daemon?

Hi @Kentzo, thank you for your question.

Could you clarify what action you are trying to perform? And perhaps share a screenshot of what you are seeing and/or the error you are encountering?

[Kentzo]

My local machine has Docker CLI only, Docker Daemon is running on another host. Microsoft's Dev Containers are configured to access it via DOCKER_CONTEXT.

When I open Dockerfile on my local machine, the Docker DX extension complains that "Docker is not running" (I assume it refers to Docker Daemon):

As I have no intention of running Docker Daemon locally, I'd like to tell Docker DX to use the remote host either by providing DOCKER_HOST or DOCKER_CONTEXT.

[Kentzo]

I'm not sure what you refer to by "works", but this is the output:

$ docker ps
Cannot connect to the Docker daemon at unix:///Users/kentzo/.docker/run/docker.sock. Is the docker daemon running? 

Which is expected, because I do not run Docker Daemon locally, only on the remote host.

[rcjsuen]

@Kentzo You see the same three warnings in your Dockerfile after running docker context use docker-vm and restarting Visual Studio Code, right?

[Kentzo]

docker context use desktop-linux (default):

docker context use docker-vm:

[Kentzo]

This is a bit inconsistent though, in another Dockerfile with docker context use desktop-linux:

Looks like that some errors are detect even when context points to a non-running Docker Daemon.

[rcjsuen]

Looks like that some errors are detect even when context points to a non-running Docker Daemon.

Correct. Sorry for not making that clear. Not all issues that the Docker DX extension flags in a Dockerfile require a running Docker daemon.