mirror of
https://github.com/docker/compose.git
synced 2026-11-17 13:45:39 +00:00
COMPOSE_REMOVE_ORPHANS and COMPOSE_IGNORE_ORPHANS resolve through different sources by design, not by accident: the destructive variable goes through the process environment, completed from the local .env only — a remote model cannot enable container removal — while the benign one reads project.Environment, remote configs included, where the worst a remote model can do is suppress a warning. Stated once, on the resolveIgnoreOrphans helper shared by up, create and run, so future reviewers don't have to rediscover the decision. The helper is covered by a test, and another one runs the real up/down/kill/run/create commands to pin that each of them resolves COMPOSE_REMOVE_ORPHANS. Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com> |
||
|---|---|---|
| .. | ||
| cmdtrace | ||
| compatibility | ||
| compose | ||
| display | ||
| formatter | ||
| prompt | ||
| main.go | ||