Universal BlueUB
Universal Blue•5mo ago
Dean Walnut

DX: VSCode can't attach to running container

For a few months now I have had the issue that VSCode can't attach to containers I created in Distrobox.
Steps:
  1. I start containers via distrobox
  2. In VSCode, I go to "Containers" on the left
  3. Right click container -> Attach Visual Studio code
  4. I get this pop-up at the bottom right:
Attaching to dev containers made in VSCode works though. 

Error running command remote-containers.attachToRunningContainerFromViewlet: Command failed: docker inspect --type container a5add931c13965049b93b2236ed87dc70aae0436344f0dc52560f6501818aff1. This is likely caused by the extension that contributes remote-containers.attachToRunningContainerFromViewlet.

In the last few months I have tried a loooooooot of things to fix this and another issue where graphical applications just wouldn't start even though I installed (I think) all dependencies. In the end I just made the problem probably a lot worse.
I tried stuff like force-installing docker, uninstalling it after no success, reinstalling podman and docker (and then disabling podman docker compat), symlinking the different socker sockets I found in the fs, and changing so many configurations that I can't possibly show them here. So my question is different: How can I
  1. remove VSCode with all its configs and reinstall,
  2. remove Podman with all its configs and reinstall,
  3. remove Docker with all its configs and reinstall,
  4. reset the symlinks for the docker sockets somehow
Since I appear to be one of few to have this problem, just resetting everything to how it was intended to have been set up from the start should fix it hopefully.

rpm-ostree status: 
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-dx-nvidia:stable
                   Digest: sha256:b95183dd8873a2fdbf1f1026a9f8e6f829ba599e4105897689a8688c4394a66e
                  Version: 42.20250731 (2025-07-31T21:25:34Z)
          LayeredPackages: coolercontrol liquidctl
                Initramfs: regenerate
...
Was this page helpful?