You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 27, 2023. It is now read-only.
when using ECS context and running docker compose up -d and thereafter immediately running docker compose ps --format=json I get an error message: unexpected end of JSON input. This is happening since updating to v1.0.14. I validated that v1.0.13 does not produce this error reverting back to that version.
#!/bin/sh# Create an ECS context
docker context create ecs myecs --from-env
# Switch to newly created context
docker context use myecs
docker compose up -d
docker compose ps --format=json # this command produces `unexpected end of JSON input`
In version 1.0.13 and lower this produces null.
Note: when doing a sleep 10 before running the ps command it does show null.
Describe the results you received:
unexpected end of JSON input
Describe the results you expected:
null as I'd get in version v1.0.13 and before (min version tested: v1.0.11)
Additional information you deem important (e.g. issue happens only occasionally):
Usecase
I use docker compose up -d to workaround issue #1084 as I want to use a cluster with Fargate Spot provider. With the JSON output I validate certain conditions with jq.
Output of docker context show:
You can also run docker context inspect context-name to give us more details but don't forget to remove sensitive content.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Description
when using ECS context and running
docker compose up -d
and thereafter immediately runningdocker compose ps --format=json
I get an error message:unexpected end of JSON input
. This is happening since updating to v1.0.14. I validated that v1.0.13 does not produce this error reverting back to that version.Steps to reproduce the issue:
Install version 1.0.14
docker-compose.yml used:
Minimal script to reproduce:
In version 1.0.13 and lower this produces
null
.Note: when doing a
sleep 10
before running theps
command it does shownull
.Describe the results you received:
unexpected end of JSON input
Describe the results you expected:
null
as I'd get in versionv1.0.13
and before (min version tested:v1.0.11
)Additional information you deem important (e.g. issue happens only occasionally):
Usecase
I use
docker compose up -d
to workaround issue #1084 as I want to use a cluster with Fargate Spot provider. With the JSON output I validate certain conditions withjq
.Output of
docker version
:Output of
docker context show
:You can also run
docker context inspect context-name
to give us more details but don't forget to remove sensitive content.Output of
docker info
:Additional environment details (AWS ECS, Azure ACI, local, etc.):
AWS ECS
The text was updated successfully, but these errors were encountered: