Branislav Osif fc860cbd1f fix: ignore one-off container events in up monitor ... `up --abort-on-container-exit` tore down the project when a one-off container created by `docker compose run` exited. The container list built in monitor.Start already excludes one-off containers via oneOffFilter(false), but the event subscription did not, and the only guard on incoming events is the service label, which a one-off container inherits from the service it was run from. Regression since v2.39.0 (last unaffected release is v2.38.2), and a recurrence of docker/compose-cli#1955, fixed there by docker/compose-cli#1987. Signed-off-by: Branislav Osif <brano@osif.digital>		2026-08-12 16:02:25 +02:00
..
api	Dedup pre_start hook images against service and each other	2026-07-30 10:40:06 +02:00
bridge	Update pkg/bridge/convert.go	2026-08-06 16:00:08 +02:00
compose	fix: ignore one-off container events in up monitor	2026-08-12 16:02:25 +02:00
dryrun	fix(cp): return non-nil Content from dry-run CopyFromContainer	2026-07-30 11:37:49 +02:00
e2e	fix: ignore one-off container events in up monitor	2026-08-12 16:02:25 +02:00
mocks	chore(deps): github.com/docker/cli v29.6.0	2026-06-22 09:00:18 +02:00
remote	fix(oci): fetch artifact layers from blobs endpoint, not via Resolve	2026-08-03 14:56:34 +02:00
utils	fix: make e2e tests pass reliably locally with Docker Desktop	2026-05-18 10:55:41 +02:00
watch	test(watch): cover the permission branches as root	2026-08-11 14:10:40 +02:00