Files
my-rook-config/images
Michael Adam 03927a7044 build: fail clearly when a usable container command is missing
When neither docker nor podman is available and usable,
`make build`, `make lint.yaml`, and `lint.markdown` used to fail
with confusing unhelpful error messages like `run: command not found`
or `build: command not found` and in the case of build fail rather late
in the process.

This change lets make fail imuch more early and with a clear error message that a
working installation of container runtime with podman or docker is required.

The new logic is this:

If docker is present and usable, use it
otherwise, if podman is present and usable, use it
otherwise, if DOCKERCMD is explicitly set to a usable command, use it.
otherwise, error out at corresponding targets.

In order to avoid adding new confusions, `make clean` and `make build` are  additionally made robust to
gracefully skip the image cleanup and image cleanuop steps, respectively,  with an informational message
instead of
failingi hard  when no usable container command is provided or detected.

Assisted-by: GitHub Copilot
Signed-off-by: Michael Adam <obnox@samba.org>
2026-07-15 16:49:22 +02:00
..