-
Notifications
You must be signed in to change notification settings - Fork 310
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 Containers fails to start when containerd
experimental Docker feature is enabled
#7214
Comments
Tested this also on Windows computer. The similar error occurs when
|
Same problem appears in windows 11 with wsl2. |
This seems to be an issue with Docker's experimental feature. I suggest to reopen docker/for-mac#6468 or open a new issue for Docker. |
@chrmarti That is doable, too, but is it possible to get any more info of how this situation looks like from within VS Code? Like the error message talks about I am also thinking - perhaps when |
So I did comparison of
Does this give any additional help on the issue? Is the |
Thanks @stazz for looking into this. We are not using |
@chrmarti Ahh, okay! Makes sense then that probably isn't related to VSCode extension. :) But at which point exactly this happens? Is VSCode invoking some This info would help probably also with the linked docker/for-win#13002 if that is indeed correct place to track this error. |
@stazz Replied there. Thanks. |
Thank you @chrmarti ! I guess this issue can be closed then? |
Let's keep it open to track the issue as it is surfacing in Dev Containers (previously named Remote-Containers). |
Hello, I am also having the same issue. I am using MacOS Monterey latest with M1 chip. There is no problem running the container in regular mode, from the terminal. These are my outputs: Error Logs
|
Hello, I have a user that is running into this issue. She is running MacOS Monterey on M1. I am waiting on confirmation of the state of the Experimental Feature. Update: Confirmed she had the feature enabled. Disabling it resolved the issue. This is her log: Error Logs
|
Confirmed to be fixed by Docker Desktop 4.13.0: docker/for-win#13002 (comment) . Worked for me too. |
mcr.microsoft.com/vscode/devcontainers/javascript-node:16-bullseye
)Steps to Reproduce:
containerd
feature of Docker DesktopRemote-Containers: Open Folder in Container...
command in VS Code to boot up container server and run VS Code via itDoes this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes
There is issue like this opened in Docker (for Mac) repo, but I think it is more suitable to be here.
I also have "New Virtualization framework" and "VirtioFS directory sharing" experimental features of Docker (for Mac) enabled, but disabling them did not seem to have any effect on this crash.
The text was updated successfully, but these errors were encountered: