microsoft / microsoft/vscode-remote-release
Attaching running container fails
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Situation
I am gratefull for the eventual revival of the podman support ( https://github.com/containers/podman/issues/17306 ), was eager to try the new extension. I was trying to attach vscode to running containers (podman) on the server, that I am connected via SSH. I could see the containers on the "Individual Containers" pane, but trying to attach results in the following error, with no visible logs.
Container tools, right click and attach error.
Error running command remote-containers.attachToRunningContainerFromViewlet: An unknown error occurred. Please consult the log for more details.. This is likely caused by the extension that contributes remote-containers.attachToRunningContainerFromViewlet.
Using Remote Explorer view, dev-containers cannot be listed, with the following error.
Remote Explorer, Dev Containers view:
Error running command remote-containers.explorerTargetsRefresh: An unknown error occurred. Please consult the log for more details.. This is likely caused by the extension that contributes remote-containers.explorerTargetsRefresh.
Here is my complete setup.
Setup
VSCode Version: 1.100.0, Commit: 19e0f9e681ecb8e5c09d8784acaa601316ca4571
ms-vscode-remote.remote-containers: 0.413.0
ms-azuretools.vscode-containers: 2.0.1
podman: 5.4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with VS Code 1.100.0, the listed remote-containers and containers extensions, Podman 5.4, and an SSH-connected server. Start from the Individual Containers attach command and the Remote Explorer refresh command, then inspect the extension logs for the underlying error. Done means both operations work with the Podman containers instead of showing an unknown error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100