Devcontainers Extensions fails to clone private dot-files repository

Describe the Bug

I finally switched off the VSCode Devcontainers extension this week after delaying for a while and I have not been able to get the devcontainer to clone and build my dot-files.

From inspection it appears that the clone is failing and then the rest of the process proceeds as normal. I don’t see the repository cloned on disk to ~/dot-files and had seen some git credential issues before I experimented.

Even ssh-agent forwarding keys to the process which builds the container would likely solve this issue.

2025-07-22 13:53:07.481 [info] [devcontainer run-user-commands][stderr]: [2025-07-22T20:53:07.516Z] Start: Run in container: # Clone & install dotfiles via 'install.sh'
2025-07-22 13:53:07.483 [info] [devcontainer run-user-commands][stderr]: [2025-07-22T20:53:07.517Z] dotfiles marker found
2025-07-22 13:53:07.483 [info] [devcontainer run-user-commands][stderr]: [2025-07-22T20:53:07.517Z]
2025-07-22 13:53:07.483 [info] [devcontainer run-user-commands][stderr]: [2025-07-22T20:53:07.517Z]
2025-07-22 13:53:07.483 [info] [devcontainer run-user-commands][stderr]: [2025-07-22T20:53:07.517Z] Stop (1 ms): Run in container: # Clone & install dotfiles via 'install.sh'
2025-07-22 13:53:07.484 [info] [devcontainer run-user-commands][stderr]: [2025-07-22T20:53:07.517Z] Start: Run in container: mkdir -p '/home/ubuntu/.devcontainer' && CONTENT="$(cat '/home/ubuntu/.devcontainer/.postStartCommandMarker' 2>/dev/null || echo ENOENT)" && [ "${CONTENT:-2025-07-22T20:50:41.908029406Z}" != '2025-07-22T20:50:41.908029406Z' ] && echo '2025-07-22T20:50:41.908029406Z' > '/home/ubuntu/.devcontainer/.postStartCommandMarker'
2025-07-22 13:53:07.486 [info] [devcontainer run-user-commands][stderr]: [2025-07-22T20:53:07.521Z]
2025-07-22 13:53:07.487 [info] [devcontainer run-user-commands][stderr]: [2025-07-22T20:53:07.521Z]
2025-07-22 13:53:07.487 [info] [devcontainer run-user-commands][stderr]: [2025-07-22T20:53:07.521Z] Exit code 1
2025-07-22 13:53:07.487 [info] [devcontainer run-user-commands][stderr]: [2025-07-22T20:53:07.521Z] Stop (4 ms): Run in container: mkdir -p '/home/ubuntu/.devcontainer' && CONTENT="$(cat '/home/ubuntu/.devcontainer/.postStartCommandMarker' 2>/dev/null || echo ENOENT)" && [ "${CONTENT:-2025-07-22T20:50:41.908029406Z}" != '2025-07-22T20:50:41.908029406Z' ] && echo '2025-07-22T20:50:41.908029406Z' > '/home/ubuntu/.devcontainer/.postStartCommandMarker'
2025-07-22 13:53:07.493 [info] [devcontainer run-user-commands]: Command completed with exit code 0
2025-07-22 13:53:07.493 [info] Devcontainer run-user-commands output: {"outcome":"success","result":"done"}

Note the command “succeeds” but returns exit code 1.

Steps to Reproduce

Try to use the dot-files feature of the devcontainers extension with a private repository.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.4
VSCode Version: 1.99.3
Commit: a8e95743c5268be73767c46944a71f4465d05c90
Date: 2025-07-10T16:53:59.659Z (1 wk ago)
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

It appears that the ssh-agent forwarding is setup after attempting to clone the git repository.

Can you reorder things so that the keys required by git are available before you call install.sh?

Related as I was debugging this: Anyspheres Dev Container Extension: Use the Name Property of DevContainers + Allow to Switch Containers - #46 by jroesch

Hi @jroesch, thank you for this bug report. We are looking into it.