Explicitly set provider runtime#406
Conversation
Improves logic around which runtime to use, making sure to always account for KIND_EXPERIMENTAL_PROVIDER environment variable setting. Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: stmcginnis The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@avosepp are you able to check this patch to confirm it fixes the problem? |
|
I compiled this with I'm not sure if this is a related to the way I'm running the app or not. But maybe these errors will help you. |
|
Thanks - that error is something unrelated to proper runtime detection, so it looks like this does do what it's intended to do. |
|
Guessing the error is maybe an environment issue? Have you seen this before @aojea? Well past the provider selection though, so this is definitely something unrelated. |
|
Wait! I'm sorry. I forgot I had Docker uninstalled. Ignore this. I uninstalled docker, then ran with sudo and the ENV flag in the same line. And it did correctly recognize it need to run with podman. Then I had the same errors in the log.txt I posted above. So it looks like yes. This fix works. Quite possibly the errors thrown in the log I uploaded above are just due to the way I built or ran the software when I self-compiled it. |
|
@stmcginnis I think that right now we can remove init() entirely.
|
Improves logic around which runtime to use, making sure to always account for KIND_EXPERIMENTAL_PROVIDER environment variable setting.
Related to: #404