We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After I upgraded the docker compose plugin to 2.21.0 (2.21.0-1~debian.11~bullseye), the gradle docker "compose up" task stopped working for me.
2.21.0-1~debian.11~bullseye
I'm getting an error
Cause: expected '<document start>', but found '{'
I assume this is because of this breaking change in the docker-compose-plugin: https://docs.docker.com/compose/release-notes/#2210
The format of docker compose ps and docker compose ps --format=json changed to better align with docker ps output. See compose#10918open_in_new.
Apparently, docker compose ps --format json returns a JSON stream instead of a JSON array now.
docker compose ps --format json
The text was updated successfully, but these errors were encountered:
Hi, thank you for the report! 👍 Could you please share a stacktrace so we could better identify the issue? 🙏
Sorry, something went wrong.
fix: Compose 2.21.0 returns newline-separated JSONs instead of single…
c4d19f9
… JSON array Fixes #420 #421
Addressed in 0.17.5 release.
Thanks for the quick fix! I tried 0.17.5, and it's working with compose 2.21.0.
No branches or pull requests
After I upgraded the docker compose plugin to 2.21.0 (
2.21.0-1~debian.11~bullseye
), the gradle docker "compose up" task stopped working for me.I'm getting an error
I assume this is because of this breaking change in the docker-compose-plugin:
https://docs.docker.com/compose/release-notes/#2210
Apparently,
docker compose ps --format json
returns a JSON stream instead of a JSON array now.The text was updated successfully, but these errors were encountered: