[BUG][Regression] docker compose run no longer respects environment variables since 2.37.2

[max-wittig]

Component	Works (v2.37.1)	Fails (v2.37.2)
Docker Compose	✅	❌

Description

As described here: #12908

Apparently now docker compose run does no longer consume environment variable so this broke our setup as we rely on http_proxy and https_proxy to be set.

We normally inject proxy variables into a build process and docker compose used to automatically used those. Now they are not even consumed, if explicitly supplied via docker compose run -e

Downgrading to 2.37.1 made it work again.

Maybe its relevant that we need to set DOCKER_BUILDKIT: 0 and that we use this command to maintain Sentry

See: https://github.com/getsentry/self-hosted/blob/494051b8df0c6e18badb701daf85b3818c170888/install/set-up-and-migrate-database.sh#L14

docker compose --profile feature-complete run --rm web upgrade --noinput --create-kafka-topics

Steps To Reproduce

No response

Compose Version

2.37.2

Docker Environment

Client:
 Version: 25.0.8
 API version: 1.44
 Go version: go1.24.2
 Git commit: 0bab007
 Built: Thu May 8 00:00:00 2025
 OS/Arch: linux/amd64
 Context: default

Server:
 Engine:
 Version: 25.0.8
 API version: 1.44 (minimum version 1.24)
 Go version: go1.24.2
 Git commit: 71907ca
 Built: Thu May 8 00:00:00 2025
 OS/Arch: linux/amd64
 Experimental: false
 containerd:
 Version: 1.7.27
 GitCommit: 05044ec0a9a75232cad458027ca83437aae3f4da
 runc:
 Version: 1.2.4
 GitCommit: 6c52b3fc541fb26fe8c374d5f58112a0a5dbda66
 docker-init:
 Version: 0.19.0
 GitCommit: de40ad0

Anything else?

No response

[glours]

Hello @max-wittig
We just merged a fix for multiples regression with run command, you can build a custom version from the main branch or use the binary for your platform available at the bottom of this page and let me know if you still have the issue?

[max-wittig]

@glours I just tried the binary and that seems to fix it.