Skip to content

Conversation

@namasl
Copy link
Contributor

@namasl namasl commented Dec 18, 2025

Allow flexibility to use either Docker or Podman for non-kind operations. Docker is still required for kind.

namasl and others added 7 commits January 9, 2026 11:32
Signed-off-by: Nick Masluk <nick@randombytes.net>
Signed-off-by: Nick Masluk <nick@randombytes.net>
Signed-off-by: Nick Masluk <nick@randombytes.net>
Signed-off-by: Nick Masluk <nick@randombytes.net>
Signed-off-by: Nick Masluk <nick@randombytes.net>
Signed-off-by: Nick Masluk <nick@randombytes.net>
- Auto-detect container runtime based on running daemon, not just CLI
  presence. If both are available, docker is preferred, but can be   overriden by setting the CONTAINER_TOOL environment variable.

- Fix typo: ecprintfho -> printf in db-start target

- Fix indentation error in check-prereqs (spaces -> tab)

- Add comprehensive container runtime documentation to DEVELOPER_GUIDE.md:
  - Compatibility matrix (Docker vs Podman by component)
  - Auto-detection behavior explanation
  - Three options for setting CONTAINER_TOOL
  - macOS Podman setup (init + start)
  - Port conflict troubleshooting
  - Mixed Docker/Podman workflow example

Signed-off-by: Andre Fredette <afredette@redhat.com>
@anfredette
Copy link
Member

I rebased this pr and updated it to work better on Macs when both Docker and Podman are available.

Copy link
Member

@anfredette anfredette left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/LGTM

@anfredette anfredette merged commit e8d100c into redhat-et:main Jan 9, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants