-
-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Packaging request for vscode-extensions.ms-vscode-remote.remote-containers #182397
Comments
For what it's worth, I've tried to use this extension with EDIT: Error reproduction steps:
The following error is output:
(full log output, |
With {
# …
environment.systemPackages = with pkgs; let
vscodiumExtensions = (with vscode-extensions; [
# …
]) ++ vscode-utils.extensionsFromVscodeMarketplace [
# …
{
publisher = "ms-vscode-remote";
name = "remote-containers";
version = "0.269.0";
sha256 = "sha256-8HY46AKbAU5W01BN4iwCUSFqTXfRbC937Gy0kvPTmn4=";
}
];
vscodium-with-extensions = pkgs.vscode-with-extensions.override {
vscode = vscodium;
vscodeExtensions = vscodiumExtensions;
};
vscode-with-extensions = pkgs.vscode-with-extensions.override {
vscodeExtensions = vscodiumExtensions;
};
in [
# …
vscodium-with-extensions
vscode-with-extensions
# …
];
# …
} in Output of
|
Yeah, it seems to be working fine now without any modifications. I'll close this as it can be added with |
I'm still getting EDIT I've been testing with the default Python 3 dev container. |
It might be worth to have this extension explicitly in NixPkgs, as it can be difficult for users to figure out,
(Edit: Re-opened inadvertently when posting this comment due to hitting the wrong button. I'll leave it open for now, though.) |
I think re-opening should be enough as it has not been packaged and it seems people are running into issues running it. |
Personally think pretty much all the Remote Development extensions (https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack) are interesting enough to have them in nixpkgs directly. As a nixpkgs user I'd expect most of the "official" VS Code extensions to be included. |
Does anyone have suggestions/workarounds on how to get this extension to work? Using the |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/using-vscode-devcontainers/29179/1 |
I have it working for me by using this: extensionsFromVscodeMarketplace [
{
publisher = "ms-vscode-remote";
name = "remote-containers";
version = "0.294.0";
sha256 = "sha256-Lnwan4jT5cQ/0ymd3skxS3cAhXZdwvKDRjzheX1Hqf4=";
}
]; |
Thanks @GGG-KILLER, but that still doesn't work for me :( Which version of VSCode are you running?
|
@robertodr I'm using the nixpkgs |
Only difference appears to be in the Linux kernel version 🤔
|
The problem was that my UID (1001) was not being remapped to the UID of the |
I had/have the same UID remapping problem as well. Do you know of any workaround that doesn't require me to change my UID? (When trying to debug this, I remember wondering why it didn't remap the UID. The extension code runs into a case where it decides "nothing to do", even though I would think it should actually do something.) |
@kenranunderscore - If you manually install the Keep in mind that if you persist the definition to a shared repo that this might cause problems if the other users don't have the same UID and it doesn't automap. |
Project description
This extension basically allows us to create a dev environment in a container which makes things easier with e.g.: .NET since it now has a workloads component that works outside of the binary installed by
dotnetCorePackages.sdk_X_Y
as well as tools that are also precompiled binaries downloaded from nuget.Metadata
The text was updated successfully, but these errors were encountered: