Error when opening CLI

[eddyuk]

Expected behavior

Clicking on docker CLI button show CLI of selected container

Actual behavior

Error presented: The null does not exist please set the correct path

Steps to reproduce the behavior

After installing docker on Ubuntu 18.04.02 (that hosted in Hyper-V env.) and installing Kitematic, whenever I want to use CLI, it gives me the error.

[vince-zeng]

I meet the same issue with Ubuntu 16.04. Don't know how to process it.

[amir1376irani]

same problem (not in vm) ubuntu 18.04 Kitematic 0.17.7 Docker version 18.09.1, build 4c52b90

even changing between "bash" and "sh" in setting didn't make change in result!

[messenger91]

Same issue in Ubuntu 18.04. Kitematic version 0.17.7. Docker version 18.09.2, build 6247962

[messenger91]

I find the solution. Just need install xterm terminal and check or change terminal path in kitematic: /usr/bin/xterm

[TonyVlcek]

Nice, thanks @doroninds. For some reason I missed this field entirely. BTW: if you use terminator you can just use /usr/bin/terminator

[vince-zeng]

Thanks! I changed it to /usr/bin/gnome-terminal. It work well now

[amir1376irani]

Thanks @doroninds. It didnt even came to my mind that kitematic developers will not check the bin folder looking for installed terminals at least xterm! Tested and both /usr/bin/gnome-terminal and /usr/bin/xterm works for me as expected. BTW: If anyone having trouble pressing arrow keys and see something like [[^A in terminal, change "Exec command shell" in kitematic setting from sh to bash.

[c4tom]

In my case, i use linux mint - mate, then i configure in

Terminal path: /usr/bin/mate-terminal

[lex-quarkie]

I tried xterm and gnome-terminal, but still have a problem - "docker-cli" buttons starts terminal session in my home dir (/~) instead of started container.

OS:Linux Mint 19.

[parham-pythian]

On elementary os, I set this to /usr/bin/io.elementary.terminal