Docker Desktop from Windows WSL2 running old containers that can't be seen or stopped

Docker Desktop
1

Running Docker Desktop with WSL2 running a Ubuntu distro, after upgrading to 4.27.1, I have old containers running on the WSL; however, I can’t see them with docker ps or turn them off.
What shows in Desktop are the containers I want running, and they show running. The problem is that one container is a reverse proxy, but Traefik is running from a container I used ages ago. I don’t know how this container is being started or how to get rid of it. I assume it isn’t the only container doing this, either.

2

First make sure you are using the right context from terminal.

docker context ls

You should see “desktop-linux”. If it is not the active context, activate it.

docker context use desktop-linux

I don’t remember, but assume the context nam would be the same in the WSL distribution. If you are using different contexts and run a seond docker daemon, not just docker desktop, you could get different results.

3

It is looking like it starts in default because the desktop-linux context is broken after the upgrade.

desktop-linux *   Docker Desktop                            npipe:////./pipe/dockerDesktopLinuxEngine

docker ps
Failed to initialize: protocol not available
4

Did you get this eror inside a WSL distribution or from Powershell on the Windows host?

5

Bash command line from WSL.

6

I encounter the same problem. Noticed it first when trying to run traefik with a watcher on docker containers and tried to point to the correct endpoint:
providers: docker: watch: true exposedByDefault: false endpoint: "npipe:////./pipe/dockerDesktopLinuxEngine"

When directly visiting the WSL distro i could see that the default context was on unix:///var/run/docker.sock and after switching to the other shown context which was the desktop-linux one I got the same error message on alle docker commands inside the WSL