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.

Sign up for GitHub

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

Jump to bottom

Can't use top in an exec pipe - "TERM not set" #759

Closed
tomwilkie opened this issue Dec 14, 2015 · 5 comments
Closed

Can't use top in an exec pipe - "TERM not set" #759

tomwilkie opened this issue Dec 14, 2015 · 5 comments
Milestone
0.13.0

Comments

@tomwilkie
Copy link
Contributor

screen shot 2015-12-14 at 11 56 07
@tomwilkie tomwilkie added this to the 0.12.0 milestone Dec 14, 2015
@foot
Copy link
Contributor

foot commented Jan 4, 2016

top works on all the alpine containers I have. execing or attaching to containers just running sh.

@tomwilkie
Copy link
Contributor Author

I think you need to do it on a container that wasn't started with -ti, such as the scope container.

@tomwilkie tomwilkie modified the milestones: 0.13.0, 0.12.0 Jan 15, 2016
@errordeveloper
Copy link
Contributor

The question is how to inject TERM on docker exec... One way would be to run /usr/bin/env TERM=xterm /bin/sh -l instead of /bin/sh (as we are currently doing).

@paulbellamy
Copy link
Contributor

top works fine on the scope container for me...
screen shot 2016-02-11 at 14 47 41

But not on the elasticsearch one. Seems like it could be an issue specifically with ubuntu?

@paulbellamy
Copy link
Contributor

Caused by this bug in docker: moby/moby#9299

@paulbellamy paulbellamy mentioned this issue Feb 17, 2016
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.13.0
Development

No branches or pull requests
4 participants
@foot @paulbellamy @errordeveloper @tomwilkie