microsoft / microsoft/vscode-remote-release
Make Podman work without setting the executable name/path
@chrmarti is already working on this.
Since Oct 12, 2020.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
vscode fails to detect podman on recent versions of Fedora (maybe similar with recent RHEL/CentOS).
It expects there to be a symlink named docker that points to podman.
On Fedora, a docker may be installed using the podman-docker package.
Probably earlier versions had a symlink, but on Fedora 32 this file is a script:
$ file docker
docker: a /usr/bin/sh script, ASCII text executable
To check for podman, vscode could check if there is a podman executable (for example by running podman version).
Related request:
It would be nice if vscode doesn't require installing the podman-docker package. That means vscode should use podman as the executable name when invoking commands instead of docker when the system has podman.
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.