-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support use with Docker #164
Comments
This issue is currently awaiting triage. |
Wouldn't it be sufficient to replace the one and only (currently) call to the Then only the installation guide (README.md) would be left with a hard coded use of |
IIUC, and please correct me if I am incorrect; the docker engine client uses the API to call into a docker to take action. While this is also supported in Podman, I can't see this as a shared, agreed-on spec in OCI. While I doubt this would change, it is just something I am a little worried about. Specifically, I am looking at this part of the [https://github.com/opencontainers/runtime-spec/blob/main/glossary.md#runtime-caller]
It sounds like there are no defined specs for external callers, but I feel like I would be more comfortable using the CLI interface because of the line around Like I said I could be incorrect, and if there is some other place to look please point me to it, I honestly have no idea, just thoughts on what I am reading. There is also the concern about having a dependency on Moby, as, in the past, this has caused me lots of pain. It may not be a real concern anymore just some past experience that I want to add to the conversation. |
Resolved in #165 |
If I look into the code of #165, I wonder how I could enforce using |
If PODMAN_BIN is set, it will use that AFAICT |
Of course, your right as the |
Right now, kantra defaults to podman to run commands in containers. An env var
PODMAN_BIN
can be used to override it with docker. We want to allow kantra to detect docker use, if available, without the user having to define this variable.The text was updated successfully, but these errors were encountered: