Avoid podman killing all containers with configuration commit?


First off working with Podman/containers in 1.4 is fantastic :raised_hands: It really adds so much to the platform.

Is there any way to avoid all containers being destroyed and rebuild when making a change to the container configuration?

I noticed this as well, ideally the only container that should restart is the one which configuration has changed for.

I created a bug report T5047

1 Like