Recreate the container if a volume file changed

[bwaldvogel]

I have a Docker Compose service that mounts some project files as volume into the container

services:
  my-service:
    …
    volumes:
      - ./my-config1.yaml:/path/in/container/my-config1.yaml:ro
      - ./my-config2.yaml:/path/in/container/my-config2.yaml:ro

To the best of my knowledge, docker compose up my-service does not restart the container if it’s already up and running, even if my-config1.yaml or my-config2.yaml changed.

Since we are using Gradle with the gradle-docker-compose-plugin anyway, I would like to leverage Gradle to track input file changes and let trigger the Docker container recreation if necessary.

Is there a recommended way to achieve this or does even gradle-docker-compose-plugin support this feature out-of-the-box?

[augi]

Hello, I think that you are referring to the reconnecting feature: https://github.com/avast/gradle-docker-compose-plugin?tab=readme-ov-file#reconnecting

The decision if the plugin should reconnect or call a new up is driven by the getStateForCache method

So maybe someone could prepare a PR that would improve this method to cover more things.