I've tried everything I know and looked up and down on stack and google.
I'm using raspbian with apache2/passenger4.0.37 Ruby 2.1.0 Rails 4.0.2.
When I try to load my site I get a 500 error and when I check apache logs I have
/usr/local/rvm/rubies/ruby-2.1.0/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:135:in `require': cannot load such file -- /phusion_passenger/platform_info/operating_system (LoadError)
from /usr/local/rvm/rubies/ruby-2.1.0/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:135:in `rescue in require'
from /usr/local/rvm/rubies/ruby-2.1.0/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:144:in `require'
from /usr/local/rvm/gems/ruby-2.1.0/gems/passenger-4.0.37/lib/phusion_passenger.rb:233:in `require_passenger_lib'
from /usr/local/rvm/gems/ruby-2.1.0/gems/passenger-4.0.37/lib/phusion_passenger/native_support.rb:68:in `libext'
from /usr/local/rvm/gems/ruby-2.1.0/gems/passenger-4.0.37/lib/phusion_passenger/native_support.rb:81:in `library_name'
from /usr/local/rvm/gems/ruby-2.1.0/gems/passenger-4.0.37/lib/phusion_passenger/native_support.rb:214:in `compile_and_load'
from /usr/local/rvm/gems/ruby-2.1.0/gems/passenger-4.0.37/lib/phusion_passenger/native_support.rb:49:in `start'
from /usr/local/rvm/gems/ruby-2.1.0/gems/passenger-4.0.37/lib/phusion_passenger/native_support.rb:376:in `<top (required)>'
from /usr/local/rvm/rubies/ruby-2.1.0/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:73:in `require'
from /usr/local/rvm/rubies/ruby-2.1.0/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:73:in `require'
from /usr/share/phusion-passenger/helper-scripts/passenger-spawn-server:79:in `<main>'
[ pid=8453 thr=3069558784 file=ext/apache2/Hooks.cpp:862 time=2014-02-14 19:47:12.154 ]: Unexpected error in mod_passenger: Cannot spawn application '/var/www/gobles': Could not read from the spawn server: Connection reset by peer (104)
Backtrace:
in 'virtual Passenger::SessionPtr Passenger::ApplicationPool::Client::get(const Passenger::PoolOptions&)' (Client.h:742)
in 'Passenger::SessionPtr Hooks::getSession(const Passenger::PoolOptions&)' (Hooks.cpp:294)
in 'int Hooks::handleRequest(request_rec*)' (Hooks.cpp:563)
There are no log files in the ruby application.
Any help would be appreciated. Thanks :D
Since we're on the path of permissions errors just figured I'd share.
ps aux | grep -i apache
Yields
root 9457 0.0 1.7 36584 7984 ? Ss 11:13 0:00 /usr/sbin/apache2 -k start
www-data 9493 0.0 1.2 36836 5696 ? S 11:13 0:00 /usr/sbin/apache2 -k start
www-data 9494 0.0 1.0 36616 4528 ? S 11:13 0:00 /usr/sbin/apache2 -k start
www-data 9495 0.0 1.2 36836 5696 ? S 11:13 0:00 /usr/sbin/apache2 -k start
www-data 9496 0.0 1.0 36616 4512 ? S 11:13 0:00 /usr/sbin/apache2 -k start
www-data 9497 0.0 1.0 36616 4512 ? S 11:13 0:00 /usr/sbin/apache2 -k start
www-data 9499 0.0 1.0 36616 4512 ? S 11:13 0:00 /usr/sbin/apache2 -k start
and for passenger
root 9460 0.0 0.3 4420 1712 ? Ssl 11:13 0:00 PassengerWatchdog
root 9467 0.0 0.5 13376 2272 ? Sl 11:13 0:00 PassengerHelperAgent
nobody 9478 0.0 0.7 11060 3212 ? Sl 11:13 0:00 PassengerLoggingAgent
and a glance at my app
drwxr-xr-x 8 root root 4096 Feb 14 18:30 app
drwxr-xr-x 2 root root 4096 Feb 14 18:30 bin
drwxr-xr-x 5 root root 4096 Feb 14 18:30 config
-rwxr-xr-x 1 root root 154 Feb 14 18:30 config.ru
drwxr-xr-x 2 root root 4096 Feb 14 18:30 db
-rwxr-xr-x 1 root root 1187 Feb 14 18:51 Gemfile
-rwxr-xr-x 1 root root 2844 Feb 14 18:52 Gemfile.lock
-rwxr-xr-x 1 root root 1187 Feb 14 22:59 Gemfile.save
drwxr-xr-x 4 root root 4096 Feb 14 18:30 lib
drwxr-xr-x 2 root root 4096 Feb 14 19:42 log
drwxr-xr-x 2 root root 4096 Feb 14 18:30 public
-rwxr-xr-x 1 root root 251 Feb 14 18:30 Rakefile
-rwxr-xr-x 1 root root 478 Feb 14 18:30 README.rdoc
drwxr-xr-x 8 root root 4096 Feb 14 18:30 test
drwxr-xr-x 3 root root 4096 Feb 14 18:30 tmp
drwxr-xr-x 3 root root 4096 Feb 14 18:30 vendor
I've tried chown www-data:www-data No luck there either.
So it seems that based on this question Cannot spawn application, the problem is that the passenger user does not have permission to run the rails application.
You can tell by looking at the log file
Cannot spawn application '/var/www/gobles': Could not read from the spawn server: Connection reset by peer (104).
One thing you could try doing, is finding out what the passenger username is, and then do a chmod -R on the /var/www/gobles directory.
Related
I'm trying to run Zalenium docker on ubuntu 18.04. Below is my command.
curl -sSL https://raw.githubusercontent.com/dosel/t/i/p | bash -s start
or
docker run --rm -ti -p 4404:4444 -v /var/run/docker.sock:/var/run/docker.sock -v /home/emiteqa/eMite/videos:/home/seluser/videos --privileged dosel/zalenium start
I got stuck at "Copying files for Dashboard"
Docker binary already present, will use that one.
Docker version 18.09.0, build 4d60db4
-- LOG 07:33:35:233537096 Ensuring docker works...
-- LOG 07:33:35:414698248 Ensuring docker-selenium is available...
haveged: haveged starting up
Copying files for Dashboard...
After investigate, I find the cause is the zalenium get hung at below line in zalenium.sh
sudo chown -R ${HOST_UID}:${HOST_GID} /home/seluser
Then, I go into the zalenium container. I try to run sudo chown on any file in the container, it get stuck.
seluser#5ada56c01231:~$ ls -ltr
total 40396
-rwxrwxr-x 1 seluser root 41277 Nov 24 15:23 zalenium.sh
-rwxrw-r-- 1 seluser root 15086 Nov 24 15:23 zalando.ico
-rwxrwxr-x 1 seluser root 770 Nov 24 15:23 wait-testingbot.sh
-rwxrwxr-x 1 seluser root 983 Nov 24 15:23 wait-saucelabs.sh
-rwxrwxr-x 1 seluser root 933 Nov 24 15:23 wait-lambdatest.sh
-rwxrwxr-x 1 seluser root 746 Nov 24 15:23 wait-cbt.sh
-rwxrwxr-x 1 seluser root 831 Nov 24 15:23 wait-browserstack.sh
-rwxrwxr-x 1 seluser root 1268 Nov 24 15:23 start-testingbot.sh
-rwxrwxr-x 1 seluser root 2679 Nov 24 15:23 start-saucelabs.sh
-rwxrwxr-x 1 seluser root 1061 Nov 24 15:23 start-lambdatest.sh
-rwxrwxr-x 1 seluser root 1078 Nov 24 15:23 start-cbt.sh
-rwxrwxr-x 1 seluser root 1287 Nov 24 15:23 start-browserstack.sh
-rwxrw-r-- 1 seluser root 2699 Nov 24 15:23 logging_info.properties
-rwxrw-r-- 1 seluser root 2738 Nov 24 15:23 logging_debug.properties
-rwxrw-r-- 1 seluser root 1082 Nov 24 15:23 logback.xml
-rwxrw-r-- 1 seluser root 2128 Nov 24 15:23 LICENSE.md
-rwxrw-r-- 1 seluser root 637 Nov 24 15:23 error.html.bak
-rwxrw-r-- 1 seluser root 10996 Nov 24 15:23 dashboard_template.html
-rwxrw-r-- 1 seluser root 4529 Nov 24 15:23 Analytics.md
-rw-rw-r-- 1 root root 41184199 Nov 24 15:23 zalenium-3.141.59v.jar
drwxrwxr-x 1 seluser root 4096 Nov 24 15:27 css
drwxrwxr-x 1 seluser root 4096 Nov 24 15:27 js
drwxrwxr-x 1 seluser root 4096 Nov 24 15:27 img
drwxrwxr-x 5 seluser seluser 4096 Dec 5 01:56 videos
-rwxrw-r-- 1 seluser seluser 3420 Dec 6 07:00 nginx.conf.bak
-rwxrw-r-- 1 seluser seluser 3404 Dec 6 07:00 nginx.conf
-rwxrw-r-- 1 seluser seluser 627 Dec 6 07:00 error.html
drwxr-xr-x 2 seluser seluser 4096 Dec 6 07:00 logs
-rw-r--r-- 1 seluser seluser 1181 Dec 6 07:00 docker_info.txt
seluser#5ada56c01231:~$ pwd
/home/seluser
seluser#5ada56c01231:~$ sudo chown seluser:seluser wait-testingbot.sh
^C^C
seluser#5ada56c01231:~$ ^C
seluser#5ada56c01231:~$ sudo chown seluser:seluser wait-testingbot.sh
seluser#5ada56c01231:~$ sudo chown seluser:seluser wait-saucelabs.sh
^C^C
seluser#5ada56c01231:~$ sudo chown seluser:seluser wait-saucelabs.sh
seluser#5ada56c01231:~$
What I have tried
If I touch a new file and run sudo chown, there is no problem.
If I CTRL+C and retry, it will pass.
By using exact same steps starting from docker installation, I can run zalenium successfully on aws
server.
I googled, but didn't find any similar issue. I know it's possibly due to env issue, but I have no clue how to troubleshoot.
Thanks in advance for any suggestion and help.
In an Ubuntu 14.4 environment, am running Passenger under Apache to serve my Rails app.
After starting apache however:
$ passenger-status
Version : 5.3.3
Date : 2018-08-10 17:08:52 -0400
Instance: DZeozT5t (Apache/2.4.7 (Ubuntu) Phusion_Passenger/5.3.3)
Phusion Passenger is currently not serving any applications.
$ passenger-config list-instances
Name PID Description
--------------------------------------------------------------------------
DZeozT5t 1438 Apache/2.4.7 (Ubuntu) Phusion_Passenger/5.3.3
It seems as if Passenger is installed and happily running, but not detecting my application.
$ cat /etc/apache2/sites-enabled/rails.conf
<VirtualHost *:80>
ServerName url.com
DocumentRoot /opt/members-only/public
PassengerRuby /usr/local/bin/ruby
<Directory "/opt/members-only/public">
Allow from all
Options FollowSymLinks
Options -MultiViews
Require all granted
</Directory>
</VirtualHost>
My apache user is www-data
/opt/members-only is a soft link to the deployment directory ( a standard rails app)
$ ls -lash /opt/members-only/
total 104K
4.0K drwxrwxr-x 16 www-data www-data 4.0K Aug 10 17:06 .
4.0K drwxr-xr-x 10 platform platform 4.0K Aug 10 16:34 ..
4.0K drwxrwxr-x 11 www-data www-data 4.0K Jul 30 22:22 app
4.0K drwxrwxr-x 2 www-data www-data 4.0K Jul 30 22:22 bin
4.0K drwxrwxr-x 2 www-data www-data 4.0K Jul 30 23:13 .bundle
4.0K drwx------ 5 www-data www-data 4.0K Aug 10 16:10 config
4.0K -rw-rw-r-- 1 www-data www-data 130 Jul 30 22:22 config.ru
4.0K drwx------ 4 www-data www-data 4.0K Jul 30 22:22 db
4.0K drwxrwxr-x 3 www-data www-data 4.0K Jul 30 22:22 doc
4.0K -rw-rw-r-- 1 www-data www-data 2.3K Aug 10 15:45 Gemfile
8.0K -rw-rw-r-- 1 www-data www-data 6.3K Aug 10 15:45 Gemfile.lock
4.0K drwxrwxr-x 4 www-data www-data 4.0K Jul 30 22:22 lib
4.0K drwxrwxr-x 2 www-data www-data 4.0K Aug 10 16:12 log
4.0K drwxr-xr-x 2 www-data www-data 4.0K Aug 10 16:33 node_modules
4.0K -rw-rw-r-- 1 www-data www-data 70 Jul 30 22:22 package.json
4.0K drwxrwxr-x 4 www-data www-data 4.0K Aug 10 16:13 public
4.0K -rw-rw-r-- 1 www-data www-data 227 Jul 30 22:22 Rakefile
4.0K -rw-rw-r-- 1 www-data www-data 374 Jul 30 22:22 README.md
4.0K drwxrwxr-x 3 www-data www-data 4.0K Jul 30 23:13 vendor
4.0K -rw-r--r-- 1 www-data www-data 86 Aug 10 16:33 yarn.lock
There are no passenger related errors in /var/log/apache2/error.log
How can I get passenger to detect my application?
I had exactly the same problem. When going through this step by step deployment:
https://www.digitalocean.com/community/tutorials/how-to-deploy-a-rails-app-with-passenger-and-apache-on-ubuntu-14-04
I realized that I had not disabled the default site or enabled mine:
sudo a2dissite 000-default
sudo a2ensite testapp
sudo service apache2 restart
I am trying to get InterActor Community Edition running on my ubuntu 16.04 machine by following the instructions on this page
http://docs.graphileon.com/interactor/Getting_started/Setup_InterActor/Installation.html
I am fine up to the point I do the docker run...-command.
Also, I have neo4j CE 3.2.5 already running at that time....
When I open the Startpage http://localhost:8000 it shows following
login page
Contrary to the description no settings page is shown.
I also opened it directly by typing localhost:8000/settings in the browser and I got the settings page obviously with missing form-inputs and no styles rendered (compared to picture on installation instruction page)
I thought files were missing, therefore did a docker exec -it interactor /bin/bash to check sources (especially js an css-files) within the running container under the directory /var/www/html/interactor/, seemed to be ok, but i do not know how the permissions have to be set, so here they are in the runing container:
root#ffb64b944023:/var/www/html/interactor# ll
total 168
drwxr-xr-x 21 www-data www-data 4096 Oct 2 18:32 ./
drwxr-xr-x 5 root root 4096 Oct 2 18:32 ../
-rw-r--r-- 1 www-data www-data 446 Sep 6 14:26 .htaccess
-rw-r----- 1 www-data www-data 90804 Sep 6 14:26 INTERACTOR_END_USER_LICENSE_AGREEMENT.pdf
drwxr-x--- 4 www-data www-data 4096 Sep 6 14:27 css/
drwxr-x--- 4 www-data www-data 4096 Sep 6 14:27 dashboard/
-rw-r----- 1 www-data www-data 5430 Jun 21 15:19 favicon.ico
-rw-r--r-- 1 www-data www-data 5738 Sep 6 14:26 favicon.png
drwxr-x--- 2 www-data www-data 4096 Sep 6 14:27 images/
-rw-r--r-- 1 www-data www-data 6929 Sep 6 14:26 index.php
drwxr-x--- 4 www-data www-data 4096 Sep 6 14:27 js/
drwxr-x--- 3 www-data www-data 4096 Oct 1 19:31 persistent/
drwxr-x--- 14 www-data www-data 4096 Sep 6 14:27 php/
drwxr-x--- 2 www-data www-data 4096 Sep 6 14:27 scripts/
drwxr-x--- 11 www-data www-data 4096 Oct 2 18:32 settings/
drwxr-x--- 2 www-data www-data 4096 Sep 6 14:27 templates/
-rw-r----- 1 www-data www-data 98 Sep 6 14:26 version.json
thus I tried to open the linked sources in the pagesource within the browser and got some of the files opened and some not, due to 403-Error.
I wonder if the provided image is somehow misconfigured regarding the permissions or if I am doing something wrong.
The strange thing is that I already had it running after I clicked all of the linked sources in the pagesource and reloaded the settings page.
When I finished playing around in interactor I used a docker stop interactor. neither a docker start interactor nor a docker restart interactor gave me a working interactor-instance back and I cannot get it working anymore...what I am doing wrong?
I can reproduce this issue but so far i cannot find a permanent solution.
The only thing to make it work is to connect to the container:
sudo docker exec -i -t interactor /bin/bash
And the run:
chown www-data:www-data /var/www/html/interactor -R
even if all the files are already set like that.
You have to do this everytime you start the container.
We are working on a fix for this.
Disclaimer: i am a developer for Graphileon.
I have a docker image https://github.com/carnellj/spmia-chapter1 which does not find its CMD ./run.sh executable although it is there in the file system.
I was able to run /bin/sh in the container, and I can ls -l:
D:\Dokumente\ws\spring-microservices\spmia-chapter1 (master)
λ docker run -i -t johncarnell/tmx-simple-service:chapter1 /bin/sh
/ # ls -l
total 56
drwxr-xr-x 2 root root 4096 Mar 3 11:20 bin
drwxr-xr-x 5 root root 360 Apr 22 07:10 dev
drwxr-xr-x 1 root root 4096 Apr 22 07:10 etc
drwxr-xr-x 2 root root 4096 Mar 3 11:20 home
drwxr-xr-x 1 root root 4096 Apr 22 06:01 lib
drwxr-xr-x 5 root root 4096 Mar 3 11:20 media
drwxr-xr-x 2 root root 4096 Mar 3 11:20 mnt
dr-xr-xr-x 123 root root 0 Apr 22 07:10 proc
drwx------ 1 root root 4096 Apr 22 07:10 root
drwxr-xr-x 2 root root 4096 Mar 3 11:20 run
-rwxr-xr-x 1 root root 245 Apr 22 06:50 run.sh
drwxr-xr-x 2 root root 4096 Mar 3 11:20 sbin
drwxr-xr-x 2 root root 4096 Mar 3 11:20 srv
dr-xr-xr-x 13 root root 0 Apr 22 07:10 sys
drwxrwxrwt 2 root root 4096 Mar 3 11:20 tmp
drwxr-xr-x 1 root root 4096 Mar 7 01:04 usr
drwxr-xr-x 1 root root 4096 Mar 7 01:04 var
/ # ./run.sh
/bin/sh: ./run.sh: not found
/ # ls run.sh
run.sh
/bin/sh does not find ./run.sh although it is there in the file system, as proven by ls run.sh. Also, cat shows the content of run.sh:
/ # cat run.sh
#!/bin/sh
echo "********************************************************"
echo "Starting simple-service "
echo "********************************************************"
java -jar /usr/local/simple-service/simple-service-0.0.1-SNAPSHOT.jar
When I run vi from sh and copy the content of run.sh into a new file myrun.sh and make myrun.sh executable, I can execute ./myrun.sh and the spring service starts.
What is going on here? Why would sh not see an executable which is there in the filesystem? Executables from PATH or executables which I add manually run fine.
I am running Docker on Windows 10.
OK the reason is, run.sh is created with Windows line endings in the docker image if you check out with automatic lf->crlf conversion. One possible solution is to tell git not to convert line endings.
I have a docker image built from ubuntu base image with few softwares installed.
i have a startup script, as below
#!/bin/bash
/usr/local/sbin/process1 -d
/usr/local/sbin/process2 -d
/bin/bash
Now I use docker-py python library to start multiple of these containers from a python file.
c = docker.Client(base_url='unix://var/run/docker.sock',
version='1.12',
timeout=10)
container = c.create_container("p12", command="/startup.sh", hostname=None, user=None,
detach=False, stdin_open=False, tty=False, mem_limit=0,
ports=None, environment=None, dns=None, volumes=None,
volumes_from=None, network_disabled=False, name=None,
entrypoint=None, cpu_shares=None, working_dir=None,
memswap_limit=0)
c.start(container, binds=None, port_bindings=None, lxc_conf=None,
publish_all_ports=False, links=None, privileged=False,
dns=None, dns_search=None, volumes_from=None, network_mode=None,
restart_policy=None, cap_add=None, cap_drop=None)
This worked fine and I can start multiple (say 3) when I tested this on a Ubuntu Desktop, Ubuntu 14.04.1 LTS and with docker-py version of 1.10. It will start the dockers and I can do a docker attach later and work on the terminal.
Now i moved my testing environment to a Ubuntu Server edition with Ubuntu 14.04.1 LTS and with docker-py version of 1.12.
The issue i see is that, when I use the same script and try to start 3 dockers, after starting process1 and process 2 as background processes, all the dockers simply exit. It appears as if /bin/bash doesnt execute at all.
If i execute the same docker image as "docker run -t -i p14 /startup.sh --> then everything is fine again. The docker is started appropriately and i get the terminal access.
The only issue is when i execute this python library.
anybody has any similar issues...any idea on how to debug this problem...or any pointers for the fix ?
Thanks,
Kiran
The difference is you're in tty (-t) mode with an open stdin (-i) when you run your docker image with docker run -t -i p14 /startup.sh, whereas you set both stdin_open=False and tty=False in your docker-py configuration.
Because your docker container has no tty and can't take any input from stdin, your call to /bin/bash has nothing to do so exits with code 0.
Try it yourself:
An open stdin with a tty
$ docker run -t -i ubuntu:14.04 /bin/bash
root#1e7eda2bba03:/# ls -la
total 7184
drwxr-xr-x 21 root root 4096 Sep 19 21:30 .
drwxr-xr-x 21 root root 4096 Sep 19 21:30 ..
-rwxr-xr-x 1 root root 0 Sep 19 21:30 .dockerenv
-rwx------ 1 root root 7279686 Jul 21 10:50 .dockerinit
drwxr-xr-x 2 root root 4096 Sep 3 03:33 bin
drwxr-xr-x 2 root root 4096 Apr 10 22:12 boot
drwxr-xr-x 4 root root 360 Sep 19 21:30 dev
drwxr-xr-x 61 root root 4096 Sep 19 21:30 etc
drwxr-xr-x 2 root root 4096 Apr 10 22:12 home
drwxr-xr-x 12 root root 4096 Sep 3 03:33 lib
drwxr-xr-x 2 root root 4096 Sep 3 03:33 lib64
drwxr-xr-x 2 root root 4096 Sep 3 03:33 media
drwxr-xr-x 2 root root 4096 Apr 10 22:12 mnt
drwxr-xr-x 2 root root 4096 Sep 3 03:33 opt
dr-xr-xr-x 240 root root 0 Sep 19 21:30 proc
drwx------ 2 root root 4096 Sep 3 03:33 root
drwxr-xr-x 7 root root 4096 Sep 3 03:33 run
drwxr-xr-x 2 root root 4096 Sep 4 18:41 sbin
drwxr-xr-x 2 root root 4096 Sep 3 03:33 srv
dr-xr-xr-x 13 root root 0 Sep 19 18:44 sys
drwxrwxrwt 2 root root 4096 Sep 4 18:41 tmp
drwxr-xr-x 10 root root 4096 Sep 3 03:33 usr
drwxr-xr-x 11 root root 4096 Sep 3 03:33 var
root#1e7eda2bba03:/#
An open stdin with no tty (i.e., no prompt, but you can still send commands via stdin)
$ docker run -i ubuntu:14.04 /bin/bash
ls -la
total 7184
drwxr-xr-x 21 root root 4096 Sep 19 21:32 .
drwxr-xr-x 21 root root 4096 Sep 19 21:32 ..
-rwxr-xr-x 1 root root 0 Sep 19 21:32 .dockerenv
-rwx------ 1 root root 7279686 Jul 21 10:50 .dockerinit
drwxr-xr-x 2 root root 4096 Sep 3 03:33 bin
drwxr-xr-x 2 root root 4096 Apr 10 22:12 boot
drwxr-xr-x 4 root root 340 Sep 19 21:32 dev
drwxr-xr-x 61 root root 4096 Sep 19 21:32 etc
drwxr-xr-x 2 root root 4096 Apr 10 22:12 home
drwxr-xr-x 12 root root 4096 Sep 3 03:33 lib
drwxr-xr-x 2 root root 4096 Sep 3 03:33 lib64
drwxr-xr-x 2 root root 4096 Sep 3 03:33 media
drwxr-xr-x 2 root root 4096 Apr 10 22:12 mnt
drwxr-xr-x 2 root root 4096 Sep 3 03:33 opt
dr-xr-xr-x 243 root root 0 Sep 19 21:32 proc
drwx------ 2 root root 4096 Sep 3 03:33 root
drwxr-xr-x 7 root root 4096 Sep 3 03:33 run
drwxr-xr-x 2 root root 4096 Sep 4 18:41 sbin
drwxr-xr-x 2 root root 4096 Sep 3 03:33 srv
dr-xr-xr-x 13 root root 0 Sep 19 18:44 sys
drwxrwxrwt 2 root root 4096 Sep 4 18:41 tmp
drwxr-xr-x 10 root root 4096 Sep 3 03:33 usr
drwxr-xr-x 11 root root 4096 Sep 3 03:33 var
A closed stdin with a tty (you can see the prompt but you can't enter any commands)
$ docker run -t ubuntu:14.04 /bin/bash
root#95904c21e5a5:/# ls -la
hello
this does nothing :(
A closed stdin with no tty - /bin/bash has nothing to do
$ docker run ubuntu:14.04 /bin/bash
$