Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feedback for: engine/reference/commandline/logs.md #293

Closed
drduke1 opened this issue Oct 20, 2016 · 3 comments
Closed

Feedback for: engine/reference/commandline/logs.md #293

drduke1 opened this issue Oct 20, 2016 · 3 comments
Assignees

Comments

@drduke1
Copy link

drduke1 commented Oct 20, 2016

URL: https://docs.docker.com/engine/reference/commandline/logs.md

Can we get an example log or the format of the log?

@mdlinville
Copy link

docker logs reads the STDERR and STDOUT for the container's final process, by default. So the answer to your question is highly dependent on the process being run. If you are using a custom logging driver, it may bypass docker logs entirely and send its output to a different host, a volume, a database, or a log aggregation server.

Some images use tricks to manipulate the output of docker logs. Have a look at the official nginx image. It uses symbolic links to be sure that the web server logs are shown as the output of docker logs.

The official Apache web server image does a similar thing, but instead of symbolic linking, it writes directly to the file descriptors for STDOUT and STDERR.

I hope this answers your question. I'll try to distill this into the documentation, though it does not belong in the command-line reference. that you linked to. That's just for the command flags, options, and syntax. In the future, if you have questions about the command-line reference or API reference, please log them in docker/docker, where those files are maintained.

Stay tuned for a PR where I capture some of the above information.

@drduke1
Copy link
Author

drduke1 commented Nov 17, 2016

That answers my question very well.

@drduke1 drduke1 closed this as completed Nov 17, 2016
joaofnfernandes pushed a commit to joaofnfernandes/docker.github.io that referenced this issue Apr 16, 2018
Also fix build breakage with `enterprise_advisory` capture.
JimGalasyn pushed a commit that referenced this issue Apr 16, 2018
Also fix build breakage with `enterprise_advisory` capture.
@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked

@docker docker locked and limited conversation to collaborators Nov 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants