Peter Rullmann

These dates indeed do not reflect what patch level users are actually getting and running. That's maybe interesting to mention in the footnotes. In your case, you have access to...

I can confirm that setting DOCKER_HOST in an .env file does not work anymore with docker compose v2. Also DOCKER_CONTEXT does not work, but would be equally handy. **Steps to...

> I have experienced the same issue as prullmann after following their procedure. The `DOCKER_HOST` variable does work for me in the `.env` file though. @hskingr Can you please elaborate...

> Had to use compose V1 as a result to read DOCKER_HOST from .env file. @trcoelho Does that work well for you? I noticed in my project that some compose...

A few days ago commit #9512 was merged that could also fix this issue. It looks like it's already included in [Compose v2.6.0](https://github.com/docker/compose/releases/tag/v2.6.0) and [Docker Desktop 4.90](https://docs.docker.com/desktop/release-notes/#docker-desktop-490) which was released...

I can confirm that neither `DOCKER_HOST` nor `DOCKER_CONTEXT` are picked up by `docker compose` v2. So no change with the latest Compose v2.6.0 / Docker 4.9.0 as hoped. ### Steps...

It seems #9512 by @ulyssessouza implemented feature request #9345 not by loading the default `.env` file or using one from the `--env-file` command line argument. Instead it's loading an `env_file`...

Hi @trcoelho, I am just a user trying to help getting this fixed. From the [git history](https://github.com/compose-spec/compose-go/commits/master), it looks like @ulyssessouza and @glours worked on issue #9521, but I can't...

> I'm wondering if I there would be a different way to change the docker daemon to point to a remote host. @requiem240sx There is DOCKER_CONTEXT, but that also doesn't...

> Upon further review, we’ve decided to not support dynamically setting `DOCKER_HOST` via `.env` files in Compose v2 (#9871). @milas Thanks for clarifying, sounds sensible so far. But what mechanism...