Cannot build container with features on rootless podman

• VSCode Version:

Version: 1.116.0
Commit: 560a9dba96f961efea7b1612916f89e5d5d4d679
Date: 2026-04-15T00:28:13Z
Electron: 39.8.7
ElectronBuildId: 13797146
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Linux x64 6.19.12-200.fc43.x86_64

• Local OS Version: Fedora Linux 43.20260418.0 (Silverblue)
• Remote OS Version: N/A
• Remote Extension/Connection Type: Dev Containers
• Logs:

remoteContainers-2026-04-20T21-46-40.394Z.log

Steps to Reproduce:

1. Install the (admittedly community provided) VSCode Flatpak
2. Install the remote development pack, including the devcontainers extension
3. Enable the podman socket via systemctl --user enable --now podman.socket
4. Add a few overrides to the flatpak:
   • flatpak override --user --filesystem /tmp com.visualstudio.code
   • flatpak override --user --filesystem xdg-run/podman com.visualstudio.code
   • flatpak override --user --filesystem xdg-run/podman/podman.socket com.visualstudio.code
   • flatpak override --user --env=CONTAINER_HOST=unix:///run/user/1000/podman/podman.sock com.visualstudio.code
5. Attempt to use the following devcontainer defintion:

   {
       "name": "test-reporter",
       "image": "mcr.microsoft.com/devcontainers/typescript-node:4-24-trixie",
       "features": {
           "ghcr.io/devcontainers/features/dotnet:2.5.0": {
               "version": "8.0",
           },
       },
   }
   

.... the container fails to start, complaining about buildkit setup.

Note that this devcontainer definition was working up until the last few days. Additionally, devcontainers work without features (which somewhat defeats the purpose); it seems to be anything which triggers buildkit, which can fail or stay failed in a number of interesting ways.
For instance, the bootstrap images often end up not fully exiting, getting stuck at "stopping":

xzero@mystery:~$ podman ps -a
CONTAINER ID  IMAGE                                                                                          COMMAND               CREATED         STATUS                             PORTS       NAMES
995562b833ab  localhost/vsc-0.454.0-d0846cf167dc09039aa9f6970026341fab03e161009cd9d54e66c35f0a3d8d3d:latest  -c echo Container...  21 hours ago    Exited (0) 17 minutes ago                      epic_saha
9cb593cf519c  localhost/vsc-volume-bootstrap:latest                                                          sleep infinity        41 minutes ago  Stopping                                       lucid_turing
cc79a64b46de  docker.io/moby/buildkit:buildx-stable-1                                                                              41 minutes ago  Exited (1) Less than a second ago              buildx_buildkit_default
8b9d9c650076  registry.fedoraproject.org/fedora-toolbox:43                                                   toolbox --log-lev...  29 minutes ago  Exited (143) 24 minutes ago                    default
9e85825ff6cd  localhost/vsc-volume-bootstrap:latest                                                          sleep infinity        7 minutes ago   Stopping                                       jolly_saha

Start with the attached remoteContainers log and the Dev Containers feature/buildkit setup path, then reproduce the failure using rootless Podman with the listed Flatpak overrides and podman socket. Check the bootstrap and BuildKit container behavior during a feature-enabled build. Done means the provided devcontainer definition builds and starts successfully with features enabled.