Skip to content

Conversation

lisongmin
Copy link
Contributor

Currently, podman-compose does not support service level configuration changes.
This means that any configuration changes will lead to a full recreation of services.

By setting service_level_change_detect: true under global x-podman key, podman-compose
will calculate a hash of the service level configuration and will only recreate
that service if the hash has changed.

@p12tic
Copy link
Collaborator

p12tic commented Aug 21, 2025

I think this could be considered a bug and thus we don't need to introduce service_level_change_detect.

Copy link
Collaborator

@p12tic p12tic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, thanks! I think we don't need service_level_change_detect though, because by default docker-compose does not recreate containers unnecessarily already.

@lisongmin lisongmin force-pushed the feat-service-level-config-hash branch from 6430c81 to 312d321 Compare August 22, 2025 01:27
@lisongmin
Copy link
Contributor Author

The service_level_change_detect flag is removed.

@lisongmin lisongmin requested a review from p12tic August 22, 2025 02:14
@p12tic p12tic merged commit a38a34a into containers:main Sep 5, 2025
8 checks passed
@lisongmin lisongmin deleted the feat-service-level-config-hash branch September 6, 2025 14:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants