Nicolas De loof
Nicolas De loof
@faustind yes. `docker compose run` _should_ use existing services previously set by `up` example: ```yaml services: web: image: nginx test: image: alpine command: ping -c 1 web depends_on: - web...
kind reminder, It's been 1 year now :)
rebased. > Can you add the alternative description (docker-compose) for those who don't have the latest Docker installation Not sure I get your point here. Compose v1 (`docker-compose`) will be...
ok, added a note.
That's indeed not a strict backward compatibility here, but with Docker Compose v2 in the wild for some time I'd prefer we don't change this behavior now As a simple...
By the way, unquoted parentheses doesn't make string an invalid bash command example: ``` #> $(which ls) toto.rb bob toto.tar compose.yml #> (which ls) /bin/ls ```
That would make sense when project directory is inferred from first file in the list, but how would this behave when user declares an explicit project directory with `docker compose...
I wonder we could adopt `__DIR__` variable used by PHP as "_folder of the current file_". I don't know another comparable example we could get inspiration for regarding syntax
AFAICT this "works as expected" and can be closed: `kill -9 31275` will kill the process, but won't send kill signal to the whole process group, like `Ctrl+C` does in...
Compose v2 _should_ also be installed as `docker-compose` in user PATH ("standalone" backward compatibility mode)