-
Notifications
You must be signed in to change notification settings - Fork 524
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
Extension doesn't recognize Docker Desktop #3811
Comments
Probably the same issue as #3806 or #3783. We're seeing a lot of cases where some part of the environment is breaking down. We think it might be external: microsoft/vscode#172124 |
@dschuessler are you able to run |
Our latest nightly build has support for additional diagnostic logging to help troubleshoot this issue. If anyone running into this problem is willing to install the nightly build (see #1408 for instructions on installing nightly builds) and provide debug logs, that would be a big help. To install the latest nightly, you'll need to be on at least version 1.74.0 of VS Code. To enable debug logging for the Docker extension, open the VS Code command palette (ctrl+shift+p on Windows and Linux) and run the Developer: Set Log Level... command. Select debug from the subsequent menu to enable debug level logs, and then make sure you have the Docker extension view open. To ensure the logs capture enough events to assist in troubleshooting, click on the refresh icons for at least the CONTAINERS and IMAGES Docker resource views. Finally, open the command palette again and run the Developer: Open Log File... command and select Docker from the list of logs. This should open a tab with diagnostics logging from the Docker extension. If this looks like it's captured enough Docker command output (you should see entries for docker container ls and docker image ls at least), you can reset your log level setting to the default of info or any other value you prefer (Developer: Set Log Level... on the command palette). Take the generated log output, remove any personal/secret information, save it to disk somewhere, and then email it to my github alias (danegsta) @microsoft.com. Please DO NOT share the logs directly in the issue comments on the off chance that they still contain personal information. |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
Followed the instructions of @danegsta and got the following logs on reloading the window.
|
@dschuessler can you try running |
From the command line, the |
That makes sense. For whatever reason, As a workaround, can you try setting the VSCode setting |
The setting works. The extension recognizes Docker now. Thank you! Let me know if I can help you with any further information. |
Glad it's working now! I'll resolve this as external to microsoft/vscode#118460, which we've opened to cover these issues with |
Docker Desktop is installed and running. Yet the extension pretends that it is not and suggests that I install it.
macOS: 12.6
VSCode: 1.74.3
Docker extension: 1.23.3
EDIT: Output of Docker extension:
The text was updated successfully, but these errors were encountered: