Failing to (re)build dev container, failing locally

• VSCode Version: 1.89.0
• Local OS Version: MacOS 14.4.1
• Remote OS Version: 5.15.0-1042-nvidia
• Remote Extension/Connection Type: Containers

• Logs:

[2024-05-10T08:23:41.805Z] Dev Containers 0.362.0 over Remote - SSH 0.110.1 in VS Code 1.89.0 (b58957e67ee1e712cebf466b995adf4c5307b2bd).
[2024-05-10T08:23:41.805Z] Host OS: linux 5.15.0-1042-nvidia
[2024-05-10T08:23:41.806Z] Host CWD: /home/gorilla/memben
[2024-05-10T08:23:41.807Z] Start: Run: /bin/sh 
[2024-05-10T08:23:42.481Z] Start: Run in host: echo ~
[2024-05-10T08:23:42.934Z] /home/gorilla
[2024-05-10T08:23:42.934Z] 
[2024-05-10T08:23:42.934Z] Stop (453 ms): Run in host: echo ~
[2024-05-10T08:23:42.935Z] Start: Run in host: id -un
[2024-05-10T08:23:43.062Z] gorilla
[2024-05-10T08:23:43.062Z] 
[2024-05-10T08:23:43.062Z] Stop (127 ms): Run in host: id -un
[2024-05-10T08:23:43.062Z] Start: Run in host:  (command -v getent >/dev/null 2>&1 && getent passwd 'gorilla' || grep -E '^gorilla|^[^:]*:[^:]*:gorilla:' /etc/passwd || true)
[2024-05-10T08:23:43.136Z] Stop (74 ms): Run in host:  (command -v getent >/dev/null 2>&1 && getent passwd 'gorilla' || grep -E '^gorilla|^[^:]*:[^:]*:gorilla:' /etc/passwd || true)
[2024-05-10T08:23:43.137Z] userEnvProbe: loginInteractiveShell (default)
[2024-05-10T08:23:43.137Z] userEnvProbe: not found in cache
[2024-05-10T08:23:43.137Z] userEnvProbe shell: /bin/bash
[2024-05-10T08:23:43.623Z] userEnvProbe PATHs:
Probe:     '/home/gorilla/.local/bin:/usr/local/cuda/bin:/opt/bin/:/home/gorilla/.local/bin:/usr/local/cuda/bin:/opt/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin'
Container: None
[2024-05-10T08:23:44.573Z] Initializing configuration support...
[2024-05-10T08:23:44.574Z] Internal initialization of dev container support package...
[2024-05-10T08:24:22.843Z] Start: Run: docker version --format {{json .}}
[2024-05-10T08:24:23.455Z] {"Client":{"Platform":{"Name":"Docker Engine - Community"},"Version":"23.0.4","ApiVersion":"1.42","DefaultAPIVersion":"1.42","GitCommit":"f480fb1","GoVersion":"go1.19.8","Os":"linux","Arch":"amd64","BuildTime":"Fri Apr 14 10:32:03 2023","Context":"rootless"},"Server":{"Platform":{"Name":"Docker Engine - Community"},"Components":[{"Name":"Engine","Version":"23.0.4","Details":{"ApiVersion":"1.42","Arch":"amd64","BuildTime":"Fri Apr 14 10:32:03 2023","Experimental":"false","GitCommit":"cbce331","GoVersion":"go1.19.8","KernelVersion":"5.15.0-1042-nvidia","MinAPIVersion":"1.12","Os":"linux"}},{"Name":"containerd","Version":"1.6.8","Details":{"GitCommit":"9cd3357b7fd7218e4aec3eae239db1f68a5a6ec6"}},{"Name":"runc","Version":"1.1.4","Details":{"GitCommit":"v1.1.4-0-g5fd4c4d"}},{"Name":"docker-init","Version":"0.19.0","Details":{"GitCommit":"de40ad0"}},{"Name":"rootlesskit","Version":"1.1.0","Details":{"ApiVersion":"1.1.1","NetworkDriver":"slirp4netns","PortDriver":"builtin","StateDir":"/tmp/rootlesskit1999516284"}},{"Name":"slirp4netns","Version":"1.0.1","Details":{"GitCommit":"6a7b16babc95b6a3056b33fb45b74a6f62262dd4"}}],"Version":"23.0.4","ApiVersion":"1.42","MinAPIVersion":"1.12","GitCommit":"cbce331","GoVersion":"go1.19.8","Os":"linux","Arch":"amd64","KernelVersion":"5.15.0-1042-nvidia","BuildTime":"2023-04-14T10:32:03.000000000+00:00"}}
[2024-05-10T08:24:23.455Z] Stop (612 ms): Run: docker version --format {{json .}}
[2024-05-10T08:24:25.716Z] TypeError: Cannot read properties of undefined (reading 'toString')
	at sU (/Users/ben/.vscode/extensions/ms-vscode-remote.remote-containers-0.362.0/dist/extension/extension.js:296:46348)

Steps to Reproduce:

1. The server where this issue occurs has a unique setup where multiple people share the same user account.
2. The issue happens only when initially building the dev container. However, I can open dev containers built by others under the same user account, and others can build my dev container, which I can then access.
3. Based on the logs, the problem seems to be local to my setup. Reinstalling VSCode (trying to do it cleanly) did not resolve the issue.
4. Other than my SSH key being password-protected, there's seems to be no difference regarding my setup to the others.

Does this issue occur when you try this locally?: No