Issue with podman-compose

[PrawinPracash]

Hey everyone, I'm running into an issue with podman-compose and hoping to get some advice.
I'm using "podman-compose up -d service1 --remove-orphans" where service1 has an updated image. The problem is that all my containers are being stopped, and only service1 is being restarted with the new image. This isn't the desired behavior; I expected just service1 to update without affecting the others.
Is this a known issue with podman-compose? Has anyone found a better way to handle service updates with Podman? I'm open to exploring alternatives to podman-compose if there's a more robust solution for managing multi-container applications in Podman. Any insights or recommendations would be greatly appreciated! Thanks!

[baude]

Have you considered asking this of the podman-compose project itself? While we share a name, I'm not aware of any podman developers who work on podman-compose. I'm not suggesting you delete this, because maybe someone who has more experience with the project will speak up. Good luck!