Closed n0ct1s-k8sh closed 4 months ago
Hi @n0ct1s-k8sh, thanks for opening the issue. We've added a small fix over here #1165 but your problem seems to be that your workspace is not aware of githubs host key. Adding this to your post create script should work:
mkdir ~/.ssh && touch ~/.ssh/known_hosts && ssh-keyscan -t rsa github.com >> ~/.ssh/known_hosts
Hi. Yes, I realized after submitting the issue, so I closed it. Thank you so much for the info!! I'll keep an eye on it
What happened?
Hi. I have some private repos in my BitBucket cloud account to work with them using their devcontainers using my personal SSH identity. Nowadays I can use them as the standalone way with VSCode, but I saw this tool and I'm giving it a try. I've created a workspace for a private repo, sourcing it from a its local folder and used the Docker provider to open it in VSCode/VSCode web. The devcontainer builds successfully but when the postCreateCommand calls a custom shell script to clone other dependent private repos, it fails:
I've searched for another issues with SSH agent forwarding and apparently they were fixed.
If I try to run the workspace, it opens successfully VSCode but if I try to run the script to clone the repos, it fails again with the same error.
What did you expect to happen instead?
I expected to build the devcontainer successfully with the postCreateCommand action and open my repo to start working on it.
How can we reproduce the bug? (as minimally and precisely as possible)
ssh-add -l
).git clone
..devcontainer
and the `devcontainer.json manifest)..devcontainer
directory of your repo:devcontainer.json
thepostCreateCommand
to run that shell script.My
devcontainer.json
:Local Environment:
DevPod Provider: