-
Notifications
You must be signed in to change notification settings - Fork 306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remote Container : Clone Repository in container volume extension 0.231.0 & sup #6571
Comments
@depoortere Could you check if the latest version of the Remote-Containers extension (currently 0.231.4) fixes this? (We have made a few fixes related to 'Clone Repository'.) |
No same problem with 0.231.5, |
Could you check if the developer console has anything logged? ( Also please append the log from the latest version, maybe that has additional hints towards what is going on. Thanks. |
Test with 0.231.6 Starting Dev Container (show log) :
Developer tools :
I use Rancher Desktop 1.2.1:
|
Unclear if related (also with Rancher Desktop): #6590 |
Does this work when cloning https://github.com/microsoft/vscode-remote-try-node ? (Reproduced #6590 with Rancher Desktop 1.2.1, but not this issue.) |
No ! [2022-05-01T16:33:13.850Z] Remote-Containers 0.231.6 in VS Code 1.66.2 (dfd34e8260c270da74b5c2d86d61aee4b6d56977). Developer Logs : |
This last log looks like #6590. Please give Remote-Containers 0.233.1 pre-release a try and let me know if that fixes it. |
Yes, it's ok when I use https://github.com/microsoft/vscode-remote-try-node, the container started. But it's not working with my own repo (gitlab on premise + vpn), block with container sleep infinity [2022-05-04T16:28:20.966Z] Remote-Containers 0.233.1 in VS Code 1.66.2 (dfd34e8260c270da74b5c2d86d61aee4b6d56977). the devconsole : |
This looks like a problem with how the |
My previous answer was made with the latest Rancher Desktop 1.3.0. Note that I'm using internal Docker images hosted on a Sonatype Nexus on premise. I don't use Microsoft's predefined images. |
I see this with Rancher Desktop when using a built-in configuration (e.g., with https://github.com/microsoft/vscode-azure-account). Do you have a path with local configurations in your settings? With: |
Yes, I use this setting to have devcontainer.json to indicate the target image of my nexus, the https_proxy setting and the extensions to install. |
Upstream issue: rancher-sandbox/rancher-desktop#2094 You could try using Rancher Desktop's WSL Integration:
I currently can't get Rancher Desktop's WLS integration working, so can't confirm if this would work. Let me know how it goes. |
If i set these parameters, nothing append : I'm trying different wsl image, start code from windows or from wsl command line, nothing append. |
That might be the same issue. What do you get for |
|
Could be an issue with the daemon then. The upstream issue rancher-sandbox/rancher-desktop#2094 is now targeted for the "next" milestone. 🤞 |
Steps to Reproduce:
1.Ctrl+Shift+P > Remote Containers : Clone in container volume ..
2.Choose "Clone a repository from Gitlab (url on premise https) in a container volume
3.Choose project in list and choose https://mygitlab/myproject remote url
4.Execution stay on the last line of this log and in
docker ps
the container vsc-volume-bootstrap stay on "sleep infinity"v0.224.3 still running correctly !
Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: N/A
The text was updated successfully, but these errors were encountered: