Dotfiles cloned before ssh-agent is started #1034
Description
What happened?
I tried to use the dotfiles feature. I prefer to keep my dotfiles repository private, so SSH authentication needs to work in the devcontainer before the dotfiles repository can be cloned. Here is part of debug log relating to this issue:
[19:43:50] debug Done executing ssh server helper command
[19:43:50] debug Done creating devcontainer
[19:43:50] info Run 'ssh svg-io.devpod' to ssh into the devcontainer
[19:43:50] info Dotfiles git repository [email protected]:martinbiard/dotfiles.git specified
[19:43:50] debug Cloning dotfiles into the devcontainer...
[19:43:50] debug Running command: [C:\Program Files\DevPod\devpod-cli.exe ssh --agent-forwarding=true --start-services=true --user dev --context default svg-io --log-output=raw --command /usr/local/bin/devpod agent workspace install-dotfiles --repository [email protected]:martinbiard/dotfiles.git --debug --debug]
[19:43:50] info Adding ssh keys to agent, disable via 'devpod context set-options -o SSH_ADD_PRIVATE_KEYS=false'
[19:43:50] info Error adding private keys to ssh-agent: ssh-agent is not started
What did you expect to happen instead?
I expected dotfiles repository to be successfully cloned, regardless of if the repository is public or private.
How can we reproduce the bug? (as minimally and precisely as possible)
Create a private dotfiles repository and try to set it up in devpod.
Local Environment:
- DevPod Version: 0.5.5
- Operating System: windows
- ARCH of the OS: AMD64
DevPod Provider:
- Local/remote provider: docker