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
It's caused by switching to docker-compose exec rather than docker exec. The -T switch apparently causes docker-compose to not wire stdin to the command.
Piping cannot work in all cases due to a bug in docker-compose. So
query docker-compose for the service container id and run docker exec
instead.
Fixes#1
It's caused by switching to
docker-compose exec
rather thandocker exec
. The -T switch apparently causesdocker-compose
to not wire stdin to the command.It's a known issue: docker/compose#3352
Our only option is reverting to using
docker exec
, but can improve on guessing the container name by usingdocker-compose ps -q <service>
.The text was updated successfully, but these errors were encountered: