-
Notifications
You must be signed in to change notification settings - Fork 303
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
trying to use podman results in "Docker version 17.06.1 or later required" #3042
Comments
We relax the version check only if the executable (after following all symlinks) is called |
I installed "podman-docker" which is a shell script wrapper around docker. I removed it and made it a symlink - now it works. |
I see, we can investigate improving that check. Remote-Containers will have a setting to specify the "Docker" CLI (which can then be |
Some additional info (Fedora 32, same issue with
Contents of
On my system (Fedora Silverblue), this area of the filesystem is intentionally immutable, so manual edits to this area aren't (easily) possible or recommended. I did a |
It may be useful to use the Running ExamplesDocker Community Edition on Ubuntu 20.04
Podman on Fedora 32 Silverblue with
|
Fixing by using |
I can't seem to figure out how to install podman-docker and it's proving an impossible phrase to search. Can anyone help verify that this is working now or provide steps on how I can verify? |
Which distribution? It's available in CentOS/Fedora's repos and the AUR. I'm using Fedora 32 and the package is able to be installed without issue. |
@DMouse10462 Yes that would explain it, I was on Ubuntu. Are you able to confirm that it works now? |
I got it to list my containers, therefore "solving" the titled issue, but couldn't actually get containers to work in practice. Existing Fedora toolbox containers failed to install the server and new containers created in VS Code couldn't access folders due to permissions issues, but these could also be Fedora Silverblue/ostree quirks. I've yet to be able to test it on a non-ostree distro as my other daily driver is Pop! OS (which uses Docker and not Podman). |
Got a Fedora Workstation 32 install running (Edit: with This is technically beyond the scope of the issue of podman not being detected at all, but if this issue represents podman support within the extension then this issue is within scope. The specific error I receive upon attempting to create a container with a repository in a new volume is as shown: Here are the contents of the built-in terminal as of the error:
The recovery container fails as well with the following logs:
|
@DMouse10462 thanks for the investigation! I'll loop in @chrmarti for how to handle this going forward. |
Using a volume is tracked as #2881. It is currently not supported. To verify: Install podman-docker and make sure Remote-Containers does not complain about Docker not being a recent enough version. |
In that case, I can verify from Fedora Workstation 32 that installing Thanks for the heads-up on issue 2881. |
Steps to Reproduce:
Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: