Max Goltzsche

Makes sense! A PR would be welcome.

@howardjohn I am afraid that this is a kpt issue: khelm runs within a container and just prints the templated manifests to stdout with paths annotated on resources (see [here](https://github.com/mgoltzsche/khelm/blob/v2.0.0-beta.4/cmd/khelm/fn.go#L204))....

@howardjohn I created a kpt feature request for this: https://github.com/GoogleContainerTools/kpt/issues/1531

That's odd. Looks like the container file system wasn't mounted (due to a silently ignored error maybe). Does it work when you run the command as root (`sudo podman ...`)?

Okay, I haven't used WSL2 yet. Does the problem also occur when you use the normal image (`mgoltzsche/podman:4.1.0`, uses `runc`) instead of the minimal image? I don't see many differences...

The minimal image comes with `crun` instead of `runc` and is configured for low isolation for a lower footprint to avoid problems when trying to run podman as unprivileged user...

@awidjaja oh, in that case the problem is probably caused by a misconfiguration within the alpine-baed image indeed. I must admit that I am using podman as unprivileged user only...

Hi @wangjia184, thanks for reporting the issue! Which image and version are you using? Also please send the podman command that you're calling. I guess you're using the `mgoltzsche/podman:3.4.2-minimal` image....

I verified that the CNI configuration file does not exist within the minimal podman image. However podman creates the file (`/etc/cni/net.d/87-podman.conflist` when run as root or `/podman/.config/cni/net.d/87-podman.conflist` when run as...

@ariansvirsky it should work if you run podman within a privileged container - you can still let it run as unprivileged user. I think it might even work without running...