microsoft / microsoft/vscode-remote-release
dev.containers.dockerPath should work as remote.containers.dockerPath did
Open
@chrmarti is already working on this.
Since Jul 27, 2023.
containers
feature-request
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
This is linked to #8393.
The new dev.containers.dockerPath setting cannot be configured on a per-remote basis and can only be configured at the application scope (i.e. "This setting has an application scope and can be set only in the user settings file").
As the linked issue states, it's common to use different container stacks on the local machine and different remote machines.
The old setting remote.containers.dockerPath used to enable a workaround in using Podman on a remote Fedora machine (see https://github.com/containers/podman/issues/15001#issuecomment-1193321924).
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.