Docker Community Forums

Share and learn in the Docker community.

Docker logs -f not following output

(Trorbyte) #1

Expected behavior

docker logs -f should follow a log file

Actual behavior

it seems the -f flag is not being honoured - it reports some entries in the log then returns


OS X: version 10.11.4 (build: 15E65) version v1.11.1-beta11
Running diagnostic tests:
[OK] docker-cli
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160512-101434.tar.gz
Most specific failure is: No error was detected
Your unique id is: 02729E0A-E09E-41FF-9FC2-75E4CD4237A4
Please quote this in all correspondence.

Steps to reproduce the behavior

  1. start an container
  2. ensure it is running; docker ps
  3. docker logs -f

(Dave Tucker) #2

@trorbyte thanks for the report.
I’ve tried to reproduce as follows but I can’t :cry:


FROM alpine
CMD ["/usr/bin/yes"]
$ docker build -t yes .
$ cid=$(docker run -itd yes)
$ docker logs -f $cid

and so on…

(Trorbyte) #3

@davetucker thanks for the quick response. Yes your example also works on my environment, so it looks to be something specific to my container (running Jira tomcat on a centos based image).

(Trorbyte) #4

committing the container and launching a new container - no issue with the log behaviour. All is working fine again.

(Dave Tucker) #5