No containers/images/etc. listed in extension when docker is installed via snap package

We've received a number of different reports recently of a particular bug on Linux systems that results in the Docker extension not showing any containers, images, etc. despite seeing one or more results when enumerating resources with the Docker CLI from the terminal. We've tracked down what we believe to be the most common root cause of the issue to the snap application sandbox blocking access to some resources when a snap install of Docker is called from a snap install of VSCode.

We're still investigating what would be required to fix this issue (or if it's something that would require an external fix somewhere like the Docker snap package itself), but we've identified a manual workaround that should unblock users of the extension. If you update the Docker Path property in your VSCode settings to /snap/docker/current/bin/docker the extension should start listing resources correctly again. If you see any errors after updating the Docker Path property, please double check that you installed Docker via snap and that it installed the Docker snap resources to the default path.

No files or tests are named. Start by reproducing the issue with snap-installed Docker and VS Code, then trace how the extension discovers and invokes the Docker CLI. Done means determining whether the extension can accommodate the snap path or whether the limitation belongs to the Docker snap, with the result verified against resource listing.