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

Add containerLogs API endpoint #12

Closed
clue opened this issue Jun 17, 2015 · 4 comments · Fixed by #53
Closed

Add containerLogs API endpoint #12

clue opened this issue Jun 17, 2015 · 4 comments · Fixed by #53
Assignees
Milestone

Comments

@clue
Copy link
Owner

clue commented Jun 17, 2015

Depends on #4 (uses raw streams?)

@clue clue modified the milestone: v0.3.0 Jun 18, 2015
@clue clue self-assigned this Aug 28, 2015
@clue
Copy link
Owner Author

clue commented Aug 28, 2015

After investigating this further it turns out this behaves very similar to the containerAtach API endpoint (#13) and uses the same framing protocol if TTY mode is not enabled.

I'll look into this.

@clue
Copy link
Owner Author

clue commented Aug 31, 2015

Looks like many API clients resort to using the inspection API to check whether TTY mode is enabled for the given container.

https://github.com/docker/docker-py/pull/669/files
https://github.com/docker/docker/blob/master/api/client/logs.go

@clue
Copy link
Owner Author

clue commented Aug 31, 2015

  • TTY disabled (default) - multiplexed stream, uses application/octet-stream content-type
  • TTY enabled - raw plaintext stream, uses text/plain content-type

@clue
Copy link
Owner Author

clue commented Aug 31, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant