Newest version fails to open existing dev container #6541
Comments
|
I have this issue too, from 0.231.0 version of Remote - Containers. Reproduced on linux and macos systems |
|
We are a research group and this issue is reproducible on macos and windows with a ubuntu host. We can't open new containers either. |
|
If you are using 'Clone Repository in Volume' with a Docker Compose config: Could be #6538. Could you try setting If that doesn't work, please also append your devcontainer.json, Dockerfile and docker-compose.yml (if any). |
|
Also check if it is fixed in Remote-Containers v0.231.2 or v0.232.2-pre-release. |
|
I may have just filed a duplicate of this in #6545 -- I am seeing this issue in vscode and vscode insiders, with both the release version of remote-containers and the 0.232.2-pre-release. |
|
Same problem. v0.232.2 is not working for me either. Downgraded to v0.224.3. |
|
@fnkr downgrading resolved the issue for you? It is not for me. |
|
@chriscasola Yes, downgrading works for me. |
|
This works for me when connecting to a remote container on an Ubuntu server. Solution: Kill existing vscode-server processes on the remote machine with the command kill -9 `ps aux | \grep vscode-server | \grep USER | \grep -v grep | awk '{print $2}'`Replace USER with the user associated to these commands (you can manually check this without the I think this problem is related to the |
|
We might be looking at two problems here. Could everyone append their log from when the problem occurs? ( |
|
This is a machine translation, so it may be difficult to understand. SystemMacBook Pro (13-inch, M1, 2020) ProjectIf only one of them is used, the problem will not occur. ProblemThe following error occurs I have formatted the devContainersSpecCLI.js to make the issue easier to understand
function Ca(t, e) {
throw t.write(Se(e)), new Error(e) // line 13198
}
var Hw = Z(require("path")); let {
config: $,
workspaceConfig: re
} = W, P = await ms(L, A);
P || Ca(B.output, "Dev container not found."); // Line 14008
let x = await vi(L, P.Id, re.workspaceFolder, $.remoteUser),
R = cc(B, x, $),
I = await lc(B, x, $, R, p);
console.log(JSON.stringify({
outcome: "success",
result: I
}))
} catch (C) {
console.error(C), await E(), process.exit(1)
}
await E(), process.exit(0)
}I solved the problem by lowering the version as well.
|
I've installed
So it seems that it only works when I use Correction: I attached the new log file but it seems to me, that it's pretty much the same as the one before. Logfile
|
|
@Mizunanari Are you using two devcontainer.json files? Using two VS Code windows? Or how do you connect to two containers if the Docker Compose setup? I think I have fixes ready for the issues shown in the logs from @MBAatEJOT and @fnkr. |
|
Fixed in v0.231.3 and v0.232.3-pre-release. (Fixes based on investigations into @MBAatEJOT's and @fnkr's logs.) @MBAatEJOT Also make sure to rebuild the container, #6538 might have left you with a container that has the workspace mounted incorrectly. @Mizunanari I will open a new issue to follow up. Thanks. |
chrmarti
added
bug
|
v0.232.3-pre-release works for me. |
Issue Type: Bug
The Versions 0.231.x fails to open an existing dev container. It works when I install version 0.224.3.
Please see the attached log.
Extension version: 0.231.1
VS Code version: Code 1.66.0 (e18005f0f1b33c29e81d732535d8c0e47cafb0b5, 2022-03-30T05:50:14.623Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No
Remote OS version: Linux x64 5.10.16.3-microsoft-standard-WSL2
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
A/B Experiments
Logfile
The text was updated successfully, but these errors were encountered: