Matt Heon
Matt Heon
@rhatdan This definitely sounds like a separate bug than Podman not firing the cleanup hooks (unless we *want* a duplicated CGroup path for some reason)? I'm betting that mount propogation...
I wouldn't mind having a way to disable this on the Podman side, though we might want to consider doing it on a per-network basis - setting those variables for...
We are doing this on the Podman side, and I haven't heard any bug reports on it.
Throwing it in `pkg/ocicni` in libpod SGTM
May I suggest something similar to Podman's [JSONDeepCopy](https://github.com/containers/podman/blob/2225c65f74b3358d810183558185a6344ef686ac/libpod/util.go#L136-L144)? Given the highly-optimized JSON libraries available, I suspect it's not significantly slower than a reflection-based solution, and it depends only on something...
As described this is a breaking change, and I see no reason for it to be. I'd add a separate table, `runtime_args`, that allows us to add per-runtime arguments for...
``` [engine.runtime_flags] crun = [ "--debug", ] runsc = [ "--config", "/usr/share/defaults/kata-containers/configuration-qemu.toml", ] ``` Similar to this
TOML formatting allows it, and it simplifies adding new entries.
We do not have this functionality. We need to add the fields to containers.conf and them modify Podman to respect them.