Dialog Error Opening Terminal
Contents |
Sign in Pricing Blog Support Search GitHub This repository Watch 2,917 Star 35,677 Fork 10,494 docker/docker Code Issues 1,809 Pull requests 147 Projects 0 Wiki Pulse Graphs New issue exec does not set TERM env when -t passed error opening terminal cygwin #9299 Closed bluepeppers opened this Issue Nov 23, 2014 · 23 comments Projects None yet error opening terminal unknown. docker Labels area/runtime kind/enhancement Milestone 1.13.0 Assignees SvenDowideit 22 participants and others bluepeppers commented Nov 23, 2014 Passing -t error opening terminal vt100 to docker run will set the TERM environment variable. Doing so to docker exec will not. This causes things like htop to not work. $ docker run -d --name foo debian bash -c "while true; sleep 1; error opening terminal msys done" 2fc4a0d2fc6d $ docker exec -ti foo env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin HOSTNAME=2fc4a0d2fc6d Or a case that the end user is more likely to experience: $ docker run -d --name foo debian bash -c "while true; sleep 1; done" 2fc4a0d2fc6d $ docker exec foo "apt-get update && apt-get install -y htop" .... $ docker exec -ti foo htop Error opening terminal: unknown. Versions and stuff: $ docker version Client version: 1.3.1 Client API version: 1.15 Go version (client):
Error Opening Terminal Unknown. Nano
go1.3.3 Git commit (client): 4e9bbfa OS/Arch (client): linux/amd64 Server version: 1.3.1 Server API version: 1.15 Go version (server): go1.3.3 Git commit (server): 4e9bbfa $ uname -a Linux hostname 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ docker -D info Containers: 186 Images: 2828 Storage Driver: aufs Root Dir: /var/lib/docker/aufs Dirs: 3206 Execution Driver: native-0.2 Kernel Version: 3.13.0-35-generic Operating System: Ubuntu 14.04.1 LTS Debug mode (server): false Debug mode (client): true Fds: 135 Goroutines: 224 EventsListeners: 1 Init Path: /usr/bin/docker WARNING: illegal base64 data at input byte 4 WARNING: No swap limit support Apologies if this has already been reported/fixed (I didn't test against master, even though I know I should!) 👍 6 dqminh commented Nov 24, 2014 @bluepeppers i think this is fixed in master. bluepeppers commented Nov 24, 2014 I don't think so. Doing some more digging, this is actually a dupe of #8631, though I'm not sure I really accept the conclusion in that issue that this is expected behaviour. The primary use case of docker exec is debugging running containers, and I know I don't habitually run my containers with -t everywhere, making docker exec a whole lot less useful. It also contradicts the principle of least surprise, imo: I would expect the terminal to behave in the same way usi
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more
Error Opening Terminal Rxvt-unicode-256color
about Stack Overflow the company Business Learn more about hiring developers or posting ads error opening terminal xterm ubuntu with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow error opening terminal xterm ncurses is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up running a program through ssh fails with “Error opening terminal: unknown.” up vote https://github.com/docker/docker/issues/9299 2 down vote favorite When I try to execute a simple command through ssh, then it is successful. e.g. #] ssh servername "echo abcd" abcd #] However, when I try the following command, it fails: #] ssh servername ~/htopmem.sh Error opening terminal: unknown. #] where the content of htopmem.sh is below. (inspired by the answer of Marwan Alsabbagh on htop output to human readable file) #!/bin/bash echo q | http://stackoverflow.com/questions/30469813/running-a-program-through-ssh-fails-with-error-opening-terminal-unknown htop | sed -r "s/\x1B\[([0-9]{1,2}(;[0-9]{1,2})?)?[m|K]//g" | ~/aha --black --line-fix | grep Mem | grep -E -o "[0-9]+/[0-9]+" If I manually ssh to the server and run htopmem, then the execution is successful: #] ./htopmem.sh 6515/24021 #] any idea on how to make the "ssh servername ~/htopmem.sh" command work? Thank you! linux bash parsing ssh pipe share|improve this question edited May 26 '15 at 23:00 asked May 26 '15 at 22:11 user2476373 418213 htop wants a terminal. have you checked the manual? There might be a switch... –Karoly Horvath May 26 '15 at 22:15 add a comment| 1 Answer 1 active oldest votes up vote 2 down vote accepted A plain ssh command like that does not have a tty (terminal). Use the -t option to force ssh to open the terminal on its way in. From the manual: -t Force pseudo-tty allocation. This can be used to execute arbitrary screen-based programs on a remote machine, which can be very useful, e.g., when implementing menu services. Multiple -t options force tty allocation, even if ssh has no local tty. So this would work (better): ssh -t servername ~/htopmem.sh share|improve this answer edited May 26 '15 at 22:19 answered May 26 '15 at 22:16 Thomas Dickey 17
and TimingData ConvertersDesign Tools and CalculatorsDirect Digital SynthesisEmbedded Vision SensingEnergy Monitoring and MeteringFPGA Reference DesignsInterface and IsolationLow Power RF TranceiversMEMS Inertial SensorsMotor Control Hardware PlatformsPower ManagementProcessors and DSPReference CircuitsRF and MicrowaveSwitches/MultiplexersTemperature SensorsVideoWide Band RF TransceiversWireless Sensor NetworksLog in0SearchSearchSearchCancelError: You don't have https://ez.analog.com/thread/18985 JavaScript enabled. This tool uses JavaScript and much of it will https://lists.gnu.org/archive/html/bug-ncurses/2005-11/msg00045.html not work correctly without it enabled. Please turn JavaScript back on and reload this page.More questions in Linux Distribution for Blackfin Where is this place located?EngineerZoneAll PlacesProcessors and DSPSoftware and Development ToolsLinux Distribution for BlackfinLog in to create and rate content, and to follow, bookmark, error opening and share content with other members.AnsweredAssumed AnsweredHow to make htop run correctly? Terminal problemQuestion asked by sina on Feb 18, 2013Latest reply on Feb 22, 2013 by Aaronwu Like • Show 0 Likes0 Comment • 3Hi,After several tries I made a clean compile of htop and it seems it works correctly on my target device.As soon as error opening terminal I ssh to my target device from my host #ssh root@target.ipand log into the target device I run #htop and I get an error message Error opening terminal: xterm-256colorEven I tried to with different SSH terminal and I still get Error opening terminal: xtermI have no clue what is wrong with my Target side or If I forgot to set special flags for the htop compilation.Is there any simple way to get the name of currently terminal which is running inside busybox . like ps -ax ? The busybox does not have tset ? command.Thanks in AdvanceNo one else has this questionMark as assumed answeredOutcomesVisibility: Linux Distribution for Blackfin527 ViewsLast modified on Feb 18, 2013 7:19 PMTags:uclinuxContent tagged with uclinuxhtopContent tagged with htopterminalContent tagged with terminalxtermContent tagged with xtermxterm-colorContent tagged with xterm-colorbusyboxContent tagged with busyboxopeningContent tagged with openingThis content has been marked as final. Show 3 comments3 RepliesNameEmail AddressWebsite AddressName(Required)Email Address(Required, will not be published)Website AddressAaronwu Feb 20, 2013 2:28 AMMark CorrectCorrect AnswerCould you narrow down the
static / Error opening terminal: linux Date: Sun, 27 Nov 2005 07:08:56 -0500 (EST) On Sun, 27 Nov 2005, Michael Setzer II wrote: First, note: the links on http://invisible-island.net/ncurses/ncurses.htmlare pointing to 5.4, which are not there any longer, but 5.5 are. Probable just needs to be updated. thanks (I thought I had updated that file). I've been working on the g4l program, which uses dialog, and have been using the dialog program that the previous author had created for use from the boot cd. version 1.0-20040731 size 717749 bytes. I saw there was a new version 1.0-20051107, but have run into some problems getting it to work. 1. downloaded the new source, extracted it, and did a ./configure, modified the makefile to add -static to the gcc line, and make on a fedora core 4 machine, and got errors. configure ncurses disabling gpm (if there's no gpm, it won't try to use the dl library). If you need gpm statically linked, I'll have to add some more configuration scripting - the various packagers kept including the conflicting wgetch() code from ncurses in their gpm packages, so I changed ncurses to use dlsym() over a year ago - that at least lets one write an _ncurses_ application to use gpm, rather than things such as w3m that introduce conflicting symbols. 2. I was able to get the exact same code to compile on a fedora core 3 machine, and it was able to config and make a static version of dialog with a size of 841914 bytes. It works from an xterm terminal, and the a term=linux (ctrl-alt F1) on a fedora Core 3 box, but I get the error "Error opening terminal: linux" when I try to run it. The TERM=linux on both the strace might show what path it is trying to open (probably it's looking for a different path for terminfo, which can be overridden by setting $TERMINFO or $TERMINFO_DIRS). For a static build, it would make sense to compile-in "linux" as a fallback. boot cd (kernel.org 2.16.4.2) and the Fedora Core 3 terminal, so it works with TERM=linux on one. I do also notice tha the new one, that works on the Fedora is showing symbols in