microsoft / microsoft/vscode-remote-release
Recovery container used as Inspect container
Open
Nobody has claimed this yet.
bug
containers
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
When there is a recovery container for a volume, inspecting that volume in a container fails because it picks up the recovery container with the volume mounted at /workspaces (by default), but expects the mount to be at /volume.
We could add an additional label to distinguish the two types of containers. See https://github.com/microsoft/vscode-remote-containers/blame/main/src/node/singleContainer.ts#L162
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.
Assessment
This issue has not been assessed yet.