You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem?
Possibly. Right now, you have to specify "podman" as the docker binary path of the Docker executor to use Podman.
Which solution do you suggest?
I'd like there to be a "Podman" executor that automatically detects the presence of Podman and uses the path it found to run Podman
Which alternative solutions exist?
Modifying the path of the Docker executor.
Additional context
The text was updated successfully, but these errors were encountered:
Hi @dylanmtaylor thanks for raising your feature request! Tbh I am not sure on this one, I don't think devpod could assume to use podman over docker simply because it is in the PATH. If podman was available and docker wasn't, this could work, but developers will likely have both and currently there is a easy way for the user to specify.
I'll keep this ticket open to track if there is more interest from the community for the feature as this is just my opinion.
Right now if you do not have both it is broken. Our organization dropped Docker Desktop in favor of Podman desktop (not my choice), as the former had a license cost associated with it. DevPod doesn't work without a workaround if you only have Podman Desktop installed, and it's not intuitive to set the docker binary path to Podman.
Is your feature request related to a problem?
Possibly. Right now, you have to specify "podman" as the docker binary path of the Docker executor to use Podman.
Which solution do you suggest?
I'd like there to be a "Podman" executor that automatically detects the presence of Podman and uses the path it found to run Podman
Which alternative solutions exist?
Modifying the path of the Docker executor.
Additional context
The text was updated successfully, but these errors were encountered: