test: use compose rm for run cleanup

[subotac]

Fixes #5112.

Update compose run test cleanup to invoke compose rm with the test's compose file and project context. The cleanup continues to stop containers and remove anonymous volumes before running compose down.

Tests:

• go test ./cmd/nerdctl/compose -run TestThisDoesNotExist
• go test ./pkg/composer -run TestThisDoesNotExist
• go test ./pkg/cmd/compose
• git diff --check

[AkihiroSuda]

Marking the PR as a draft as the CI is failing. Please click Ready for review when ready.

[subotac]

The remaining CI failures appear unrelated to this change:

• Both ARM jobs failed during host provisioning with dpkg exit code 1, before the integration tests ran.
• The Kubernetes job timed out in TestKubeCommitSave.
• The old rootful Ubuntu job failed TestCreateFromOCIArchive.

All jobs exercising the changed Compose run tests passed, including Docker, regular rootful/rootless Linux, EL rootful/rootless, and old-rootless Linux. The corresponding ARM and old-rootful jobs also pass in the latest main test run, and Kubernetes passes in the latest main flaky-workflow run.

I attempted to rerun only the failed jobs, but GitHub requires repository admin permission for these upstream runs. Could you please rerun them?

[AkihiroSuda]

Both ARM jobs failed during host provisioning with dpkg exit code 1, before the integration tests ran.

This was recently fixed in the main branch. Please try rebasing.

[subotac]

The full matrix has now completed. The rebase resolved the ARM provisioning failure, and none of the remaining failures is in the changed Compose test file.

The seven failed jobs consist of:

• the Docker auto-remove attach race described above;
• five failures in existing image save/load tests (TestSave, TestSaveQuiet, and TestLoadQuiet), with errors such as unrecognized image format, truncated archives, and short reads;
• an old-rootful TestIPFSCompNoBuild failure caused by a Kubo API readiness timeout.

This PR only changes cmd/nerdctl/compose/compose_run_linux_test.go. More importantly, the exact base commit 5fbf7bdc also fails image-save tests in rootless and gomodjail jobs and TestIPFSCompNoBuild in rootful in the main workflow run. These failures therefore reproduce without this PR.

Could you please rerun the failed jobs?

[subotac]

Thanks for the rerun. All rerun jobs except the gomodjail/rootless job are now green.

The remaining job passed the entire Compose package (cmd/nerdctl/compose, 7m48s) and failed only in the unchanged cmd/nerdctl/image/image_save_test.go:

• TestSaveContent: the produced tar ended with Unexpected EOF in archive;
• TestSave/Image_with_different_names,_by_id: loading the archive returned unrecognized image format.

That file is byte-identical to main. The first attempt of this same job failed a different image load test, and the exact base commit's main gomodjail job failed another image-save test. This is the same recurring image-archive flake and is unrelated to the Compose-only change.

Could you please rerun just this remaining job?

[AkihiroSuda]

Thanks