in docker-compose.yml no longer displays console output

  • I have tried with the latest version of Docker Desktop
  • I have tried disabling enabled experimental features
  • I have uploaded Diagnostics
  • Diagnostics ID:

Expected behavior

Console output from services running that have tty: true in the docker-compose.yml will display

Actual behavior

After updating to Docker Desktop / Mac 4.6.0 (75818), any services that have tty: true in the docker-compose.yml no longer display

The containers are actually running just fine, and I can see the logs in the Docker Desktop application, but they are no longer visible in the console.

Removing the tty: true line from the docker-compose.yml file causes it to output as expected

I have both these Experimental features on:

  • Use the new Virtualization framework
  • Enable VirtioFS accelerated directory sharing

…but turning them off and restarting Docker Desktop did not change the lack of logging

Information

  • macOS Version: 12.2.1 (21D62)
  • Intel chip or Apple chip: Apple M1 Max
  • Docker Desktop Version: 4.6.0 (75818)

Output of /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check

I have both these Experimental features on:

  • Use the new Virtualization framework
  • Enable VirtioFS accelerated directory sharing

…but turning them off and restarting Docker Desktop did not change the lack of logging

Starting diagnostics

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0031: does the Docker API work?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0011: are the LinuxKit services running?
[FAIL] DD0016: is the LinuxKit VM running? vm is not running: vm has not started
[PASS] DD0001: is the application running?
[PASS] DD0018: does the host support virtualization?
[FAIL] DD0017: can a VM be started? vm has not started: vm has not started
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0007: is the backend responding?
[PASS] DD0014: are the backend processes running?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[PASS] DD0012: is the VM networking working?
[PASS] DD0032: do Docker networks overlap with host IPs?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0019: is the com.docker.vmnetd process responding?
[PASS] DD0033: does the host have Internet access?

Please investigate the following 1 issue:

1 : The test: can a VM be started?
Failed with: vm has not started: vm has not started

The Docker engine runs inside a Linux VM. Therefore we must be able to start Virtual Machines.

Steps to reproduce the behavior

  1. Set tty: true on a service in the docker-compose.yml
  2. Do docker-compose up
  3. See lack out output from service

2 thoughts on “in docker-compose.yml no longer displays console output

  1. This is a frustrating fix. We use tty: true so we can attach to containers for interactive debugging, e.g. byebug in Ruby, but most of the time we also want to see container output without having to run a separate terminal window to follow the logs…

Comments are closed.