Support better isulation when building images as part of kube play

[ifireball]

Feature request description

podman kube play has a useful option to build an image when the image specified in the K8s YAML maps to a directory with a Dockerfile or a Container file in it.

Currently when images are built this way, the isolation use is hard-coded to "cheroot" as evident by this code.

This can cause more complex container builds to fail due to e.g. collisions with resources running on the host.

Suggest potential solution

I would like to have at least one of the following:

• If nothing else, document the current behaviour - it took us quite a while to figure out why images that build properly with podman build fail to build with podman kube play
• A command-line option to set the desired isolation level
• Support for the BUILDAH_ISOLATION environment variable
• A way the specify the isolation via the k8s YAML file (E.g. via a POD annotation)
• Default to higher isolation level (OCI or rootless)

Have you considered any alternatives?

We are currently telling people to build the images on their own via podman build before spinning up their environment via podman kube play. We may also end up providing our own wrapper script, but this is cumbersome. We'd really like to have a single command to spin up a work environment.

Additional context

Add any other context or screenshots about the feature request here.

[rhatdan]

Interested in doing any of this yourself?

@flouthoc WDYT?

[flouthoc]

Yes I think podman play kube must honor BUILDAH_ISOLATION or must have a higher level CLI flag.

[flouthoc]

I'll check this.

[github-actions]

A friendly reminder that this issue had no activity for 30 days.

[rhatdan]

@flouthoc any update?