[Fix] docker compose --parallel ignored in Compose v5

[flopez7]

Issue tracking

Closes #3796

Context behind the change

Removed reliance on Compose-native parallel flags and moves concurrency control to shell-level parallelization with xargs -P $(DOCKER_PARALLEL), preserving the existing DOCKER_PARALLEL knob and current target behavior (with and without explicit service names).

How has this been tested?

Ran functional validation locally:

• DOCKER_PARALLEL=1 make -C docker-setup build-services
• DOCKER_PARALLEL=4 make -C docker-setup build-services
  Confirmed effective concurrency differs between 1 and 4.

Release plan

None

Potential risks; What to monitor; Rollback plan

Check:

• Local make build-services and make services-up execution time.
• Resource usage spikes on users machines.
• Any startup failures related to service dependency timing.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
human-app	Ready	Preview, Comment	Feb 20, 2026 2:47pm
human-dashboard-frontend	Ready	Preview, Comment	Feb 20, 2026 2:47pm
staking-dashboard	Ready	Preview, Comment	Feb 20, 2026 2:47pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
faucet-frontend	Ignored	Preview	Feb 20, 2026 2:47pm
faucet-server	Ignored	Preview	Feb 20, 2026 2:47pm

[dnechay]

Also I would suggest default parallelism to 2 so it's kinda guaranteed on any machine.

The reasoning is that previously docker engine itself was controlling how many services to build in parallel, but now we actually just run build command passing some specific service names and in case some depends on another - it will trigger dep service build as well exceeding the concurrency param