Closed smulvih2 closed 7 months ago
Seems its fixed in the subsequent release?
Will test the new release if available and report back
Ok ya so updating from docker 25.0.4 (docker compose 2.24.7) to docker 26.0.0 (docker compose 2.25.0) fixed the issue for me. Wanted to log this issue when I ran into it, caught me off guard as I didn't update docker or related packages when this started happening. Closing ticket now.
I'm using the latest version of docker compose, and running a
docker compose up -d
now results in:Looks like docker compose 2.24.6 introduces this breaking change, see related issue - https://github.com/docker/compose/issues/11544