I have a lead.
I'm still working on this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1290691
And when I do this:
[root@f23a ~]# docker run --net=host --pid=host -v /dev:/dev
--privileged=true fedext /usr/sbin/iotop -d3
Traceback (most recent call last):
File "/usr/sbin/iotop", line 17, in <module>
main()
File "/usr/lib/python2.7/site-packages/iotop/ui.py", line 631, in main
main_loop()
File "/usr/lib/python2.7/site-packages/iotop/ui.py", line 621, in
<lambda>
main_loop = lambda: run_iotop(options)
File "/usr/lib/python2.7/site-packages/iotop/ui.py", line 508, in run_iotop
return curses.wrapper(run_iotop_window, options)
File "/usr/lib64/python2.7/curses/wrapper.py", line 22, in wrapper
stdscr = curses.initscr()
File "/usr/lib64/python2.7/curses/__init__.py", line 33, in initscr
fd=_sys.__stdout__.fileno())
_curses.error: setupterm: could not find terminal
After that traceback, any attempt to ssh to the host is munged as
previously described. So somehow that docker command puts the host in
a state where subsequent ssh attempts fail.
Stopping docker and sshd, then starting sshd then docker, doesn't
help. I still can't login.
So is this a docker bug?
Chris Murphy