Debian Question posted in
The oficial documentation can be found here.

No live output from containers running on Docker Desktop with WSL2 – Debian

I’m developing an python-django app running in docker containers (django, celery, postgres, redist…etc). It runs on Windows 10 with WSL2-Debian & Docker Desktop.

During my work I need to observe the consoles of all those containers, so I can monitor apps behavior, like when you run docker-compose up so you got all of them live.

When you click on the container within windowed Docker Desktop app you can see the container’s console output, but not actual – it looks like it works until some point of time and there are no updates of the consoles output.
I remember it was working live just prior to a two or three Docker Desktop updates, and I’m sure it was real time there, but not now.

Did I change a setting or Docker Desktop was bugged?

PS. When I start my containers with docker-compose up (without -d) I can observe live logs on my shell console, but not in Docker Desktop anymore.

Any help how to restore Docker Desktop live console view?

Tags:

2

Answers


  1. Chosen as BEST ANSWER
    0

    It's a bug in Docker Desktop v3.3.3

    GitHub issue: https://github.com/docker/for-win/issues/11251 as pointed by @Drarig29


  2. 0

    The Docker Desktop 3.4 (released June 9th, yesterday) is supposed to have resolved docker/for-win issue 11251.

    I don’t see the error after upgrading (with the normal docker-compose, not the beta docker-compose v2).

    However, as commented by the OP twk and in issue 11251:

    the live log is somehow broken – extra newline is added after every new line, but historical log entries (Eg. when you switch to/from another container) are displayed without newlines between entries (which is OK).

    Update June 29th from Mathieu Champlon

    Sorry it took a while but we now have an internal build that should fix it, if you wanted to give it a try:
    win/stable/amd64/66242/Docker Desktop Installer.exe

    Update Aug. 2021: Issue 11251 just closed with:

    Docker Desktop 3.6.0 has been released containing a fix for this issue.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search