hashicorp / hashicorp/nomad

proposal: docker driver should detect and reject podman

Open
#13,259 3 comments 1 reaction 0 assignees View on GitHub
stage/needs-discussion theme/driver theme/driver/docker theme/fingerprint type/enhancement
Dominant language
Go
Stars
17k
Forks
2.1k
Avg merge
1d 9h
Merged PRs (30d)
105

Description

In https://github.com/hashicorp/nomad-driver-podman/issues/165 we've encountered unfortunate cases where the `docker` driver detects Podman 4.0 as if it were actually Docker. But unfortunately the fidelity of Podman's API is not quite 100% and this has caused conflict between the `podman` and `docker` drivers if they're running on the same machine.

We should at the very least provide documentation describing how to disable the `docker` driver if you're using the `podman` driver. But it may also be worth having the `docker` driver try to fingerprint Podman and refuse to send it API calls. But this leads to a bit of a conundrum as Podman's Docker fidelity gets better over time; at some point we may want to allow the `docker` driver to "just work" with Podman instead.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the docker driver entry point and the existing documentation for running the docker and podman drivers together. Determine whether the intended outcome is documentation, Podman fingerprinting, or both, and define how compatibility changes over time before implementation; the work is done when the chosen behavior prevents the reported driver conflict or clearly documents how to avoid it.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go
Domain
devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.