Stanislav Zhuk

using dump from DDEV v1.24.1 and `mysql:8.0`: 1. ✅ `ddev delete -Oy && ddev config --database=mysql:8.0 && ddev import-db --file=/path/to/dump.sql.gz` 2. ✅ `ddev debug migrate-database mysql:8.4` 3. ✅ `ddev delete...

I compared `ddev import-db` for `mysql:8.0` dump (22 GB unzipped) and tested it on `--database=mysql:8.0` in v1.24.1 and in this PR, and got the same import time ~75 minutes. However,...

> The interesting thing to me is why there is a difference between ddev describe and the value of DDEV_PRIMARY_URL in the container? - https://github.com/ddev/ddev/issues/7221

Moving to draft until I understand how DDEV handles default config values. If it doesn't work as I expected, it's not a big deal to partially revert my last commit...

> But it did _not_ work with `global` on my setup: > > ```shell > $ ddev config global --database= > # alert signal. > $ ddev config global --database...

> If you use `ddev start` instead, then `DDEV_PRIMARY_URL` always has a value It doesn't for me, at least on Linux. The issue is that the port is randomly assigned...

I found out that running `docker-compose config` on a *running* project adds the `published` ports: ```diff services: web: ports: - mode: ingress host_ip: 127.0.0.1 target: 80 + published: "32916" protocol:...

I investigated why the binary size is so big, this comes from the telemetry: - https://github.com/docker/cli/pull/4889#pullrequestreview-1914189938 > I think integrating otel things into the cli like this could cause some...

Yes, that's correct. The initial increase in size was from 17 MB to 33 MB, in the previous rebase, that's why I looked at this.

I removed `DOCKER_HOST` from here. `DOCKER_CONTEXT` and `DOCKER_HOST` are fully respected without using them directly.