search

rocker-org / rocker

R configurations for Docker
https://rocker-project.org
GNU General Public License v2.0
1.46k stars 271 forks source link

Problem loading rocker/rstudio #90

Closed kdaily closed 9 years ago

kdaily commented 9 years ago

Upon running the command, I get no access to an rstudio instance in the browser.

$ docker run -d -p 8787:8787 rocker/rstudio
5d6c0e5e63eebe2e0d032371dae9d798a30e7b2d1e29fc37d46d0cea71549cff
$ docker ps
CONTAINER ID        IMAGE                   COMMAND                CREATED             STATUS              PORTS                    NAMES
5d6c0e5e63ee        rocker/rstudio:latest   "/usr/bin/supervisor   5 seconds ago       Up 4 seconds        0.0.0.0:8787->8787/tcp   jovial_bartik       
$ docker logs 5d6c0e5e63ee
/usr/lib/python2.7/dist-packages/supervisor/options.py:296: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
  'Supervisord is running as root and it is searching '
2014-11-19 19:30:01,822 CRIT Supervisor running as root (no user in config file)
2014-11-19 19:30:01,822 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2014-11-19 19:30:01,829 INFO RPC interface 'supervisor' initialized
2014-11-19 19:30:01,829 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2014-11-19 19:30:01,829 INFO supervisord started with pid 1
2014-11-19 19:30:02,831 INFO spawned: 'rserver' with pid 8
2014-11-19 19:30:02,832 INFO spawned: 'userconf' with pid 9
2014-11-19 19:30:02,840 INFO exited: rserver (exit status 0; not expected)
2014-11-19 19:30:03,795 INFO exited: userconf (exit status 0; not expected)
2014-11-19 19:30:04,796 INFO spawned: 'rserver' with pid 54
2014-11-19 19:30:04,797 INFO spawned: 'userconf' with pid 55
2014-11-19 19:30:04,802 INFO exited: rserver (exit status 0; not expected)
2014-11-19 19:30:04,877 INFO exited: userconf (exit status 0; not expected)
2014-11-19 19:30:05,395 CRIT reaped unknown pid 57)
2014-11-19 19:30:07,398 INFO spawned: 'rserver' with pid 86
2014-11-19 19:30:07,399 INFO spawned: 'userconf' with pid 87
2014-11-19 19:30:07,403 INFO exited: rserver (exit status 0; not expected)
2014-11-19 19:30:07,487 INFO exited: userconf (exit status 0; not expected)
2014-11-19 19:30:07,986 CRIT reaped unknown pid 89)
2014-11-19 19:30:10,990 INFO spawned: 'rserver' with pid 118
2014-11-19 19:30:10,990 INFO spawned: 'userconf' with pid 119
2014-11-19 19:30:10,995 INFO exited: rserver (exit status 0; not expected)
2014-11-19 19:30:10,995 INFO gave up: rserver entered FATAL state, too many start retries too quickly
2014-11-19 19:30:11,071 INFO exited: userconf (exit status 0; not expected)
2014-11-19 19:30:11,587 INFO gave up: userconf entered FATAL state, too many start retries too quickly
2014-11-19 19:30:11,587 CRIT reaped unknown pid 121)
$ docker images -q rocker/rstudio
4522526298cc
$ docker version
Client version: 1.3.0
Client API version: 1.15
Go version (client): go1.3.3
Git commit (client): c78088f/1.3.0
OS/Arch (client): linux/amd64
Server version: 1.3.0
Server API version: 1.15
Go version (server): go1.3.3
Git commit (server): c78088f/1.3.0
$ cat /etc/redhat-release 
Fedora release 20 (Heisenbug)
cboettig commented 9 years ago

Strange, this all looks good to me and I cannot reproduce your error. You're sure you are trying the correct URL and have waited a few seconds for rstudio-server to start up (it usually takes a few seconds after the container launches on my machine, I see by your docker ps it's not been long...) What do you see? just 'web page not available' or the equivalent? What browser? You're running this locally and not on a remote server or virtualbox?

On Wed Nov 19 2014 at 1:33:45 PM Kenneth Daily notifications@github.com wrote:

Upon running the command, I get no access to an rstudio instance in the browser.

$ docker run -d -p 8787:8787 rocker/rstudio 5d6c0e5e63eebe2e0d032371dae9d798a30e7b2d1e29fc37d46d0cea71549cff

$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 5d6c0e5e63ee rocker/rstudio:latest "/usr/bin/supervisor 5 seconds ago Up 4 seconds 0.0.0.0:8787->8787/tcp jovial_bartik

$ docker logs 5d6c0e5e63ee /usr/lib/python2.7/dist-packages/supervisor/options.py:296: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security. 'Supervisord is running as root and it is searching ' 2014-11-19 19:30:01,822 CRIT Supervisor running as root (no user in config file) 2014-11-19 19:30:01,822 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing 2014-11-19 19:30:01,829 INFO RPC interface 'supervisor' initialized 2014-11-19 19:30:01,829 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2014-11-19 19:30:01,829 INFO supervisord started with pid 1 2014-11-19 19:30:02,831 INFO spawned: 'rserver' with pid 8 2014-11-19 19:30:02,832 INFO spawned: 'userconf' with pid 9 2014-11-19 19:30:02,840 INFO exited: rserver (exit status 0; not expected) 2014-11-19 19:30:03,795 INFO exited: userconf (exit status 0; not expected) 2014-11-19 19:30:04,796 INFO spawned: 'rserver' with pid 54 2014-11-19 19:30:04,797 INFO spawned: 'userconf' with pid 55 2014-11-19 19:30:04,802 INFO exited: rserver (exit status 0; not expected) 2014-11-19 19:30:04,877 INFO exited: userconf (exit status 0; not expected) 2014-11-19 19:30:05,395 CRIT reaped unknown pid 57) 2014-11-19 19:30:07,398 INFO spawned: 'rserver' with pid 86 2014-11-19 19:30:07,399 INFO spawned: 'userconf' with pid 87 2014-11-19 19:30:07,403 INFO exited: rserver (exit status 0; not expected) 2014-11-19 19:30:07,487 INFO exited: userconf (exit status 0; not expected) 2014-11-19 19:30:07,986 CRIT reaped unknown pid 89) 2014-11-19 19:30:10,990 INFO spawned: 'rserver' with pid 118 2014-11-19 19:30:10,990 INFO spawned: 'userconf' with pid 119 2014-11-19 19:30:10,995 INFO exited: rserver (exit status 0; not expected) 2014-11-19 19:30:10,995 INFO gave up: rserver entered FATAL state, too many start retries too quickly 2014-11-19 19:30:11,071 INFO exited: userconf (exit status 0; not expected) 2014-11-19 19:30:11,587 INFO gave up: userconf entered FATAL state, too many start retries too quickly 2014-11-19 19:30:11,587 CRIT reaped unknown pid 121)

$ docker images -q rocker/rstudio 4522526298cc

$ docker version Client version: 1.3.0 Client API version: 1.15 Go version (client): go1.3.3 Git commit (client): c78088f/1.3.0 OS/Arch (client): linux/amd64 Server version: 1.3.0 Server API version: 1.15 Go version (server): go1.3.3 Git commit (server): c78088f/1.3.0

$ cat /etc/redhat-release Fedora release 20 (Heisenbug)

— Reply to this email directly or view it on GitHub https://github.com/rocker-org/rocker/issues/90.

kdaily commented 9 years ago

Hi Carl,

I used http://localhost:8787/ as well as http://127.0.0.1:8787/ (according to the wiki page). I also tried the IP for docker ethernet interface (docker0, 172.17.42.1), no dice. I waited 5 or more minutes as well.

In the browser (Chrome or Firefox) I get Error code: ERR_CONNECTION_RESET.

I'm running locally.

cboettig commented 9 years ago

Hmm, well, let's dive in and poke around. Try logging into a terminal on your container and see if rserver is running?

docker exec -it <container-id> bash
ps aux | grep rserver

If it is not, try running supervisord and see if that makes a difference?

kdaily commented 9 years ago

Looks like rserver is running! Can't start another supervisord (as expected)...

$ docker exec -it b3485c7f65f7 bash
root@b3485c7f65f7:/# 
root@b3485c7f65f7:/# ps aux | grep rserver
rstudio+    11  0.0  0.0 195124  6284 ?        Ssl  21:44   0:00 /usr/lib/rstudio-server/bin/rserver
root       156  0.0  0.0  12716  2184 ?        S+   22:41   0:00 grep rserver
root@b3485c7f65f7:/# supervisord 
/usr/lib/python2.7/dist-packages/supervisor/options.py:296: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
  'Supervisord is running as root and it is searching '
2014-11-19 22:42:02,418 CRIT Supervisor running as root (no user in config file)
2014-11-19 22:42:02,418 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
Error: Another program is already listening on a port that one of our HTTP servers is configured to use.  Shut this program down first before starting supervisord.
For help, use /usr/bin/supervisord -h
kdaily commented 9 years ago

I ran an update for Fedora and it pulled docker 1.3.1, and it works fine now. However I get the same log output, so I doubt that's what fixed it. I had a kernel update which forced a restart, so I think that it must have been something else blocking...I hope that it wasn't adding to the docker group (which should be noted that docker's documentation indicates that after 1.0 adding to the docker group was not necessary). If it pops up again I'll open this up with more diagnostics.