Use the container runtime API to run krm functions instead of docker commands.

[coillteoir]

Eschewed features

• This issue is not requesting templating, unstuctured edits, build-time side-effects from args or env vars, or any other eschewed feature.

What would you like to have added?

Currently, KRM functions will use a docker command to run the specified image in a KRM function.

kustomize/kyaml/fn/runtime/container/container.go

Line 200 in 278dd6e

return "docker", a

I propose instead of using a docker command, instead using the apis of the container runtime directly.

Why is this needed?

If the docker command isn't in your path, KRM functions will not run.

As more container runtimes arise, this poses a long term risk to the UX of KRM functions.

Can you accomplish the motivating task without this feature, and if so, how?

• Installing docker.
• Creating a symlink between your container runtimes cli and 'docker'.

What other solutions have you considered?

Allowing for the container runtime command to be configurable via the kustomization or transformer yaml.

Anything else we should know?

No response

Feature ownership

• I am interested in contributing this feature myself! 🎉

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.