Nicolas De Loof 207a3eb6f7 test(e2e): reproduce --project-directory ignored on an oci:// project ... TestOciRemoteProjectDirectory publishes a project whose only service mounts a relative volume, then runs `up` on the oci:// artifact with an explicit --project-directory pointing elsewhere. The relative volume must resolve against that directory. It currently fails against the pinned compose-go: LoadConfigFiles defaults the working dir to the downloaded artifact's own cache directory whenever a remote resource loader is involved, silently overriding the explicit --project-directory the same way it would a mere default -- docker/compose#14224. On Docker Desktop this surfaces as a hard failure (the cache directory isn't a shared mount); on Linux it silently mounts the wrong directory, matching the original report. New BindMountSource check (pkg/e2e/checks.go) pins a service's bind mount source to an exact expected path, for tests that need to verify which working directory a relative volume path resolved against. Needs the compose-go fix (github.com/ndeloof/compose-go@a626c70, branch 14224-working-dir) to pass -- not yet reflected in go.mod here. Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>		2026-09-23 10:56:23 +02:00
..
api	build(deps): adopt compose-go jobs and the container-spec layering	2026-09-21 16:35:20 +02:00
bridge	build(deps): adopt compose-go jobs and the container-spec layering	2026-09-21 16:35:20 +02:00
compose	fix(up): catch a late starter on a graceful teardown too, not just on-exit	2026-09-22 14:45:23 +02:00
dryrun	fix(dry-run): commit no longer creates a real image; the interception set becomes declarative	2026-09-16 13:44:21 +02:00
e2e	test(e2e): reproduce --project-directory ignored on an oci:// project	2026-09-23 10:56:23 +02:00
mocks
remote
utils
watch