microsoft
dev.containers.dockerPath should work as remote.containers.dockerPath did
This is linked to #8393.
The new dev.containers.dockerPath setting cannot be configured on a per-remote basis and can only be configured at the application scope (i.e. "This setting has an application scope and can be set only in the user settings file").
As the linked issue states, it's common to use different container stacks on the local machine and different remote machines.
The old setting remote.containers.dockerPath used to enable a workaround in using Podman on a remote Fedora machine (see https://github.com/containers/podman/issues/15001#issuecomment-1193321924).
Or even different "local" scopes - I run multiple WSL distros on my machine: I use Podman on my personal distro, and Docker on a work-related one.
#8393 was closed because it was 1 upvote short. It's 2025, and this issue is beyond annoying when trying to work on dozens of different VM's, or any remote machines in general, that host a container server.
Having to comment out dev.containers.dockerPath in user settings for one remote container just to uncomment it for another, dozens of times per day, is just stupid at this point.
Please, prioritize this. It doesn't appear to be a complicated change, for what seems like a migration from user settings to at least workspace level. I can even imagine it being a few lines to simply check workspace settings instead of user and Bob's your uncle.
