Endless upgrades of Dev Containers
Is there an existing issue for this bug?
- [x] I have searched the existing open issues and found none that apply.
- [x] If I find any issue of interest that is related or closed, I will included a link to it in this issue.
Required Troubleshooting Steps
- [x] I have read and performed the troubleshooting steps
- [x] I have tried both values of the
remote.SSH.useLocalServersetting - [x] My issue was not covered in the Tips and Tricks linked from the Troubleshooting Wiki.
- [x] I will include a complete copy of my Remote - SSH logs by running Remote-SSH: Show Log in the command palette or from View > Output in the menu bar
[Optional] Diagnose with Copilot
I asked @remote-ssh and it helped, but I still want to report this bug
In step 2 of the troubleshooting wiki, what was the result of running the generated SSH command verbatim outside of VS Code?
I did not try step 2 of the troubleshooting steps
Remote-SSH Log
Remote-SSH Log
[15:15:56.605] Log Level: 2
[15:15:56.610] VS Code version: 1.100.2
[15:15:56.610] Remote-SSH version: [email protected]
[15:15:56.610] linux x64
Expected Behavior
Stop the endless installations and upgrades of this extension.
Actual Behavior
- This is the latest version.
- However, endless installations and upgrades occurred.
- It reverted to the latest version.
Steps To Reproduce
- VS Code version: 1.100.2
- Linux Mint 21.3 x86_64
- Dev Containers version: 0.413.0
Anything else?
No response
Do you see anything in the window or server output logs? Please attach those both so we can take a look
cc/ @sandy081
Do you see anything in the
windoworserveroutput logs? Please attach those both so we can take a lookcc/ @sandy081
Sadly, the only log I have seen is
[15:15:56.605] Log Level: 2
[15:15:56.610] VS Code version: 1.100.2
[15:15:56.610] Remote-SSH version: [email protected]
[15:15:56.610] linux x64
The new VSCode and SSH have a certain impact. I have already returned VSCode and SSH, so there is no problem and they cannot be updated or upgraded
Hey @joshspicer, this issue might need further attention.
@BrikeX, you can help us out by closing this issue if the problem no longer exists, or adding more information.