Nicolas De loof

@thaJeztah can you please unasign this issue, I'm obviously not actively working on it :)

This is basically the same I proposed as https://github.com/compose-spec/compose-go/pull/572 which was rejected as this introduce portability issues. Also, runtime.GOARCH is very specific to golang, I'd prefer we rely on `uname`...

Please check you have `OTEL_TRACES_EXPORTER` variable set. `none` value is supported but should be lowercase

This is not the default value, this `None` (uppercase) is probably set in your environment.

Can you please try running `docker buildx build .` to build your Dockerfile and confirm you get a distinct behavior ?

I can't tell what's wrong here. `OTEL_METRICS_EXPORTER` is the standard variable used to configure opentelemetry (https://opentelemetry.io/docs/languages/sdk-configuration/general/#otel_metrics_exporter) and value is set by end user's environment, not compose. Have you checked you...

Documentation is highly confusing regarding .env file, a rewrite is on its way (https://github.com/docker/docs/pull/19541) `.env` in your working directory is used to interpolate variables in your compose.yaml file, as described...

Please provide compose version in use as requested on issue template Regarding this issue, please confirm `docker pull ` detects a new image is available for target reference, while `docker...

I can't reproduce. ``` $ docker compose --progress=plain up Image xx Pulling Image xx Pulled ``` please confirm `docker pull ` detects a new image is available for target reference,...

Do you mean compose is still using the older image _even_ after `docker pull` pulled an updated one ?