Dialog Error Opening Terminal Unknown
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 unknown nano #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
Ncurses Error Opening Terminal Unknown
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 Cygwin
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 vt100 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
2010-04-08 04:52:01 synthead Member From: Seattle Registered: 2006-05-09 Posts: 1,326 [solved] Error opening terminal: unknown. [max@gayforceone jornadalin]$ htop Error opening terminal: unknown.What's going on here? I've updated my system a error opening terminal msys few times, but that's it. My headless server is doing this too. error opening terminal rxvt-unicode-256color Last edited by synthead (2010-04-08 20:35:12) Touch my kernel Offline #2 2010-04-08 05:55:53 pseudonomous Member Registered: 2008-04-23 Posts: error opening terminal xterm ubuntu 349 Re: [solved] Error opening terminal: unknown. what $TERM are you trying to run htop in?Edit:I've got to sleep but here are some ideas that occur to me (htop https://github.com/docker/docker/issues/9299 is working fine on my box), but maybe:1) TERM isn't set or is set to term type that htop can't deal with, htop should be able to deal with "TERM=xterm", also I know it handles "linux" and "screen.linux", because I just started htop in each of those settings.2) Permissions on the /dev if you're trying to run htop from https://bbs.archlinux.org/viewtopic.php?id=94780 a tty, various problems with allocating terminals can occur if something screwy happens, like you mount / read-only, is / mounted read-only? Last edited by pseudonomous (2010-04-08 06:02:16) ... imagine I'm making this argument without referencing cartoons. Offline #3 2010-04-08 12:05:31 synthead Member From: Seattle Registered: 2006-05-09 Posts: 1,326 Re: [solved] Error opening terminal: unknown. This is from XFCE's terminal. If I run xterm and run htop out of it, it works. htop isn't the only app that is complaining about the terminal right now though Example::: Starting full system upgrade... resolving dependencies... looking for inter-conflicts... Targets (9): dbus-python-0.83.1-1 feh-1.4.2-2 grep-2.6.3-1 jack-0.118.0-2 libmodplug-0.8.8-1 pixman-0.18.0-1 vte-0.24.0-2 xorg-xinit-1.2.1-1 youtube-dl-2010.04.04-1 Total Download Size: 1.33 MB Total Installed Size: 7.99 MB Proceed with installation? [Y/n] :: Retrieving packages from core... grep-2.6.3-1-i686.p... 135.6K 371.0K/s 00:00:00 [#####################] 100% :: Retrieving packages from extra... dbus-python-0.83.1-... 107.0K 338.0K/s 00:00:00 [#####################] 100% feh-1.4.2-2-i686.pk... 218.6K 454.7K/s 00:00:00 [#####################] 100% jack-0.118.0-2-i686... 239.8K 501.0K/s 00:00:00 [#####################] 100% libmodplug-0.8.8-1-... 150.5K 389.9K/s 00:00:00 [#####################] 100% pixman-0.18.0-1-i68... 140.1K 364.3K/s 00:00:00 [#####################] 100% vte-0.24.0-2-i686.p... 344.4K 609.4K/s 00:00:01 [#####################] 100% xorg-xinit-1.2.1-1-... 13.5K 16
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 JavaScript https://ez.analog.com/thread/18985 enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page.More questions in Linux Distribution https://bugs.kde.org/show_bug.cgi?id=116700 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, and share content error opening 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 I ssh to my target error opening terminal 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 Blackfin528 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 problem? for example, does htop run correctly from local console? doe
initscr() ) Summary Debugging program crash on ncurses init ( initscr() ) Status RESOLVED INVALID Product: kdevelop Classification: Unclassified Component: CPP Debugger Version: 3.3.0 Platform: Mandriva RPMs Linux Importance: NOR normal with 21 votes (vote) TargetMilestone: --- Assigned To: kdevelop-bugs-null URL: Keywords: Depends on: Blocks: Show dependency tree /graph Reported: 2005-11-19 12:51 UTC by JoĆ£o Vitor P. Moraes Modified: 2007-06-02 18:47 UTC (History) CC List: 1 user (show) dmk See Also: Latest Commit: Version Fixed In: Description JoĆ£o Vitor P. Moraes 2005-11-19 12:51:40 UTC Version: 3.3 (using KDE KDE 3.4.2) Installed from: Mandriva RPMs OS: Linux I want to debug a application using the ncurses library. But the debugger on kdevelop crashes during the initscr() call. If i'm using the IO Window the program just exit with code 01 on the initscr(); line and if the IO window is off i get "Error opening terminal: unknown" if i change the the "debugging shell" the debugger does not works (IO Window open and close very fast (Unknown option '-fullname')) i found this error marked as resolved on KDevelop 3.1.2, wich the code can "be run and stepped-through fine" but i'm using KDevelop 3.3 and this bug is back. code used: #include