Djordje Lukic
Djordje Lukic
Glad you made it work! We'll update the docs, add a paragraph about cloning over SSH. @DewZ89 could you try and do the same thing @Dids did and tell us...
Hi @Maxime-p, thanks for opening this issue, Jetbrains announced recently [the remote development feature](https://www.jetbrains.com/help/idea/2021.3/remote-development-starting-page.html), we are looking at making this a first-class citizen of Dev Environments. We will keep you...
If yes, please send me an email at [email protected] ;)
This is not possible today unfortunately since the remote containers extension can't run on vscodium :/
Hey all, thank you for all the diagnostic ids, could you also provide us with the output of these lines: ``` $ which git $ which code ``` Thanks!
> I'm sure there's a good reason for the workspace folder to be `/com.docker.devenvironments.code` The main reason is that it's a unique (and yes, weird) name so that there is...
Hey @slecache thanks for opening this, We have identified the problem and are working on a fix. Even though the error message is not the same this is a duplicate...
Hi @Nordes, Cloning over SSH only works if you have the SSH key loaded into the ssh-agent. Could you try and add your key to the agent and re-clone?
@zeroZshadow do you mean pageant? Could you run this in a power shell `[System.IO.Directory]::GetFiles("\\.\\pipe\\")` and tell us if you see a pipe named `openssh-ssh-agent` please?
Thanks! Do you see a `pageant` pipe in that command? Do you happen to have the `SSH_AUTH_SOCK` environment variable set?