intermittent error running docker compose up

[adoroszlai]

Description

Ubuntu 24.04 runner image version 20250504.1.0 has Docker Compose 2.35.1, which is affected by docker/compose#12747

Image version 20250427.1.0 had Docker Compose 2.27.1, which did not have the bug.

Please roll back to previous image version or upgrade Docker Compose to 2.36.0.

Platforms affected

• Azure DevOps
• GitHub Actions - Standard Runners
• GitHub Actions - Larger Runners

Runner images affected

• Ubuntu 22.04
• Ubuntu 24.04
• macOS 13
• macOS 13 Arm64
• macOS 14
• macOS 14 Arm64
• macOS 15
• macOS 15 Arm64
• Windows Server 2019
• Windows Server 2022
• Windows Server 2025

Image version and build link

20250504.1.0

https://github.com/apache/ozone/actions/runs/14856073950/job/41804480380?pr=8248#step:13:21

Is it regression?

yes

Expected behavior

docker compose up works

Actual behavior

docker compose up intermittently fails with fatal error: concurrent map writes

Repro steps

docker/compose#12747 (comment)

[RaviAkshintala]

Hi @adoroszlai Thank you for bringing this issue to our attention. We will look into this issue and will update you after investigating.


[kishorekumar-anchala]

Hi @adoroszlai - Could you kindly proceed with the resolution steps provided by the official team? This serves as a good workaround, allowing us to avoid upgrading to the new version, and I believe this issue might be temporary. Please feel free to reach out if you have any questions

[adoroszlai]

@kishorekumar-anchala Can you please clarify which resolution steps you mean? I don't see any in the comments on the Docker Compose bug report.

I have worked around the bug by limiting Docker Compose parallel operations to 1 (export COMPOSE_PARALLEL_LIMIT=1). However, this is not optimal, since it needs to be set for each affected workflow by all users of Docker Compose. I think it would be much better in the long run to upgrade to a version with the fix.

[kishorekumar-anchala]

@kishorekumar-anchala Can you please clarify which resolution steps you mean? I don't see any in the comments on the Docker Compose bug report.

To minimize concurrent issues, kindly consider pre-pulling the images and retrying until the new version rollout is completed.

For reference, please find the comment provided by @samifruit514:
docker/compose#12747 (comment)

[kishorekumar-anchala]

Hi @adoroszlai - Could you please confirm whether the above workaround has been tried? I would appreciate it if you could verify once it's tested.

[adoroszlai]

@kishorekumar-anchala,

As I mentioned:

I have worked around the bug by limiting Docker Compose parallel operations to 1 (export COMPOSE_PARALLEL_LIMIT=1).

This is much simpler than separate pull with retry.

[kishorekumar-anchala]

Could you please confirm one last thing before we proceed? Have you tested this with the newer version mentioned above, and did it work as expected?

cc @adoroszlai