Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Watch: exec mode

Abierto
  • ¿Algo no está bien?
#14,326 1 comentario 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@glours ya está trabajando en esto.

Desde el 12/10/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

kind/feature
Description

In https://github.com/docker/compose/pull/12330, sync+exec mode was introduced as a watch action.

I would like to request an additional action that only performs the exec part, without syncing any files.

Use case

My application code is bind-mounted into the container using volumes. On files changes I don't need the files copied in, as the volume mount already takes care of that, only a command run inside the container: here, rr reset to restart the RoadRunner workers, which is much faster than restarting the whole container.

sync+exec is the only action that runs a command, so I use it at the moment. But syncing into the bind-mounted path writes the files back onto the host (with the container user's ownership and second-precision timestamps). The watcher sees its own write as a new change and syncs again, so it loops every second.

My current workaround is to sync into a throwaway path inside the container just to trigger the exec:

develop:
  watch:
    - action: sync+exec
      path: ./src
      target: /tmp/src-watch   # throwaway; ./src is already bind-mounted at /code/src
      exec:
        command: rr reset http

This avoids triggering the endless loop described above.

Proposal

An exec action that runs the exec command on a change and takes no target:

develop:
  watch:
    - action: exec
      path: ./src
      exec:
        command: rr reset http

Thank you!

Related:
Lenguaje dominante
Go
Estrellas
38.4k
Forks
5.9k
Merge medio
2 d 5 h
PR fusionados (30 d)
62

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de docker/compose

Todos los issues de docker/compose

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.