dive icon indicating copy to clipboard operation
dive copied to clipboard

container-engine configuration not affecting operation

Open mirettig opened this issue 3 months ago • 0 comments

What happened: Using the dive.yaml configuration container-engine: podman, dive does not assume that podman is the source for a regular dive command, but will build using podman with dive build. I do not have the docker socket activated, so dive does not start.

What you expected to happen: I expect the dive command to assume --source podman when container-engine: podman is set.

How to reproduce it (as minimally and precisely as possible): Don't have docker installed/turn on, have podman installed, set container-engine: podman in a dive configuration file, try to use dive without building an image.

Anything else we need to know?: Dive version 0.13.1 podman 3.4.4 I do not have docker installed on my wsl instance, which means no docker socket.

Environment:

  • OS version
    • wsl ubuntu 22.04.5

mirettig avatar Sep 16 '25 16:09 mirettig