Docker container log does not keep streaming

[ekitagawa]

Description

Command docker container logs --tail 5 -f <id> lists one set of outputs, and then it ends instead of streaming newer entries. Is this a design limitation?

docker container run -d --name pinger microsoft/nanoserver ping 8.8.8.8 -t
docker container logs --tail 5 -f pinger

Over on Linux side, equivalent command writes last 5 lines, and then keep adding more.

docker container run -d --name pinger centos ping 8.8.8.8
docker container logs --tail 5 -f pinger

Steps to reproduce the issue:

1. Run following command on Windows engine.

   docker container run -d --name pinger microsoft/nanoserver ping 8.8.8.8 -t
   docker container logs --tail 5 -f pinger

2. Watch the output after first batch of ping output.

Describe the results you received:

First set of output comes out, and then it stops.

Describe the results you expected:

Subsequent output should be streamed.

Additional information you deem important (e.g. issue happens only occasionally):

N/A

Output of docker version:

Windows

Client:
 Version:      17.06.1-ee-2
 API version:  1.30
 Go version:   go1.8.3
 Git commit:   8e43158
 Built:        Wed Aug 23 21:16:53 2017
 OS/Arch:      windows/amd64

Server:
 Version:      17.06.1-ee-2
 API version:  1.30 (minimum version 1.24)
 Go version:   go1.8.3
 Git commit:   8e43158
 Built:        Wed Aug 23 21:25:53 2017
 OS/Arch:      windows/amd64
 Experimental: false

Linux used for comparison

Client:
 Version:      17.06.1-ee-2
 API version:  1.30
 Go version:   go1.8.3
 Git commit:   8e43158
 Built:        Wed Aug 23 21:15:00 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.06.1-ee-2
 API version:  1.30 (minimum version 1.12)
 Go version:   go1.8.3
 Git commit:   8e43158
 Built:        Wed Aug 23 21:17:30 2017
 OS/Arch:      linux/amd64
 Experimental: false

Output of docker info:

Containers: 4
 Running: 3
 Paused: 0
 Stopped: 1
Images: 3
Server Version: 17.06.1-ee-2
Storage Driver: windowsfilter
 Windows:
Logging Driver: json-file
Plugins:
 Volume: local
 Network: l2bridge l2tunnel nat null overlay transparent
 Log: awslogs etwlogs fluentd json-file logentries splunk syslog
Swarm: active
 NodeID: qn96w5vkplgofvjyds2req8uo
 Is Manager: false
 Node Address: 10.0.5.130
 Manager Addresses:
  10.0.10.119:2377
  10.0.13.107:2377
  10.0.43.96:2377
Default Isolation: process
Kernel Version: 10.0 14393 (14393.1480.amd64fre.rs1_release.170706-2004)
Operating System: Windows Server 2016 Datacenter
OSType: windows
Architecture: x86_64
CPUs: 8
Total Memory: 30GiB
Name: EC2AMAZ-RILCBEP
ID: VZIV:QABT:63VB:KUOW:4FOR:BTTB:QULZ:U7KS:CIZK:QWTU:63SI:65EG
Docker Root Dir: C:\ProgramData\docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

Additional environment details (AWS, VirtualBox, physical, etc.):

[friism]

Is this a dupe of this? https://github.com/moby/moby/issues/30046

[robinharwood]

We hugely appreciate your contribution, feedback, and support to our technical documentation.

We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.

All issues will be migrated by Thursday 29th August 2024.

Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.