e611a189cb
If a logdriver doesn't register a callback function to validate log options, it won't be usable. Fix the journald driver by adding a dummy validator. Teach the client and the daemon's "logs" logic that the server can also supply "logs" data via the "journald" driver. Update documentation and tests that depend on error messages. Add support for reading log data from the systemd journal to the journald log driver. The internal logic uses a goroutine to scan the journal for matching entries after any specified cutoff time, formats the messages from those entries as JSONLog messages, and stuffs the results down a pipe whose reading end we hand back to the caller. If we are missing any of the 'linux', 'cgo', or 'journald' build tags, however, we don't implement a reader, so the 'logs' endpoint will still return an error. Make the necessary changes to the build setup to ensure that support for reading container logs from the systemd journal is built. Rename the Jmap member of the journald logdriver's struct to "vars" to make it non-public, and to make it easier to tell that it's just there to hold additional variable values that we want journald to record along with log data that we're sending to it. In the client, don't assume that we know which logdrivers the server implements, and remove the check that looks at the server. It's redundant because the server already knows, and the check also makes using older clients with newer servers (which may have new logdrivers in them) unnecessarily hard. When we try to "logs" and have to report that the container's logdriver doesn't support reading, send the error message through the might-be-a-multiplexer so that clients which are expecting multiplexed data will be able to properly display the error, instead of tripping over the data and printing a less helpful "Unrecognized input header" error. Signed-off-by: Nalin Dahyabhai <nalin@redhat.com> (github: nalind) |
||
|---|---|---|
| .. | ||
| _static | ||
| images | ||
| README.md | ||
| docker-io_api.md | ||
| docker_io_accounts_api.md | ||
| docker_remote_api.md | ||
| docker_remote_api_v1.0.md | ||
| docker_remote_api_v1.1.md | ||
| docker_remote_api_v1.2.md | ||
| docker_remote_api_v1.3.md | ||
| docker_remote_api_v1.4.md | ||
| docker_remote_api_v1.5.md | ||
| docker_remote_api_v1.6.md | ||
| docker_remote_api_v1.7.md | ||
| docker_remote_api_v1.8.md | ||
| docker_remote_api_v1.9.md | ||
| docker_remote_api_v1.10.md | ||
| docker_remote_api_v1.11.md | ||
| docker_remote_api_v1.12.md | ||
| docker_remote_api_v1.13.md | ||
| docker_remote_api_v1.14.md | ||
| docker_remote_api_v1.15.md | ||
| docker_remote_api_v1.16.md | ||
| docker_remote_api_v1.17.md | ||
| docker_remote_api_v1.18.md | ||
| docker_remote_api_v1.19.md | ||
| docker_remote_api_v1.20.md | ||
| docker_remote_api_v1.21.md | ||
| hub_registry_spec.md | ||
| registry_api.md | ||
| registry_api_client_libraries.md | ||
| remote_api_client_libraries.md | ||
README.md
This directory holds the authoritative specifications of APIs defined and implemented by Docker. Currently this includes:
- The remote API by which a docker node can be queried over HTTP
- The registry API by which a docker node can download and upload images for storage and sharing
- The index search API by which a docker node can search the public index for images to download
- The docker.io OAuth and accounts API which 3rd party services can use to access account information