avast/gradle-docker-compose-plugin

Recreate the container if a volume file changed

Aperta

#444 aperta il 25 giu 2024

 (1 commento) (0 reazioni) (0 assegnatari)Groovy (103 fork)batch import
help wanted

Metriche repository

Star
 (429 stelle)
Metriche merge PR
 (Merge medio 24g 11h) (2 PR mergiate in 30 g)

Descrizione

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?

Guida contributor