"Unable to connect to service" when attempting to mount volume. about rocker

[eddelbuettel]

Can you detail

• which OS you
• which Docker container(s) you tried
• what command you launched
• what you were expecting
• which error you get

With the amount of detail provided here we cannot possibly help you.

[tshauck]

Yep

• Ubuntu 14.04
• rocker/rstudio, I'm on master.
• I'm not sure what you mean, but guessing: I build with docker build -t rstudio/local . Then I ran docker run -d -p 8787:8787 -v /home/thauck:/home/rstudio rstudio/local It does not work. I ran docker run -d -p 8787:8787 rstudio/local which does.
• To be able to login
• The "Unable to connect to service" error I mentioned.
  

[eddelbuettel]

Why do you build an image? You didn't exactly motivate that. And if what you build breaks, you get to keep the pieces.

We give you pre-built containers which work for us. On Linux (dev env for @cboettig and me), on Windows when I test at work, and on Windows for @benmarwick.

Because I do not know what you did to create 'rstudio/local' I am not so sure I can even try to help you.

[eddelbuettel]

Also see the Wiki -- @benmarwick has put a lot of hints in there for debugging. In his case, different vmware version caused hickups.

For you, I would really recommend you bisect first and see if our image works for you. Then build it locally, if you must -- but unaltered. Only then would I try modifications.

[tshauck]

Ok, I'll give it look. If I still have troubles, I'll reopen this.

Thanks

[tshauck]

Getting bit by this again.

I tried fresh install on a GCE image running backports-debian-7-wheezy-v20141021. Docker was installed via curl -sSL https://get.docker.com/ | sh.

I'm docker pull rocker/hadleyverse to get the image. Like last time docker run -d -p 8787:8787 -v /home/thauck:/home/rstudio rocker/hadleyverse does not work, while w/o the -v /home/thauck:home/rstudio does. Same situation with rocker/rstudio.

EDIT: Possibly related to the last answer on https://support.rstudio.com/hc/communities/public/questions/200646688-RStudio-Server-Unable-To-Connect-To-Service? Or something docker specific.

logs:

thauck@th-ds-01:~$ docker logs f93428d1bb8183fca466b64363f39932ae84bff1125a3312b89f7a09e17ec84f
/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-01 18:22:41,919 CRIT Supervisor running as root (no user in config file)
2014-11-01 18:22:41,919 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2014-11-01 18:22:41,929 INFO RPC interface 'supervisor' initialized
2014-11-01 18:22:41,929 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2014-11-01 18:22:41,929 INFO supervisord started with pid 1
2014-11-01 18:22:42,931 INFO spawned: 'rserver' with pid 10
2014-11-01 18:22:42,933 INFO spawned: 'userconf' with pid 11
2014-11-01 18:22:42,943 INFO exited: rserver (exit status 0; not expected)
2014-11-01 18:22:43,515 INFO exited: userconf (exit status 0; not expected)
2014-11-01 18:22:44,518 INFO spawned: 'rserver' with pid 55
2014-11-01 18:22:44,519 INFO spawned: 'userconf' with pid 56
2014-11-01 18:22:44,530 INFO exited: rserver (exit status 0; not expected)
2014-11-01 18:22:44,605 INFO exited: userconf (exit status 0; not expected)
2014-11-01 18:22:45,050 CRIT reaped unknown pid 57)
2014-11-01 18:22:47,054 INFO spawned: 'rserver' with pid 83
2014-11-01 18:22:47,055 INFO spawned: 'userconf' with pid 84
2014-11-01 18:22:47,064 INFO exited: rserver (exit status 0; not expected)
2014-11-01 18:22:47,140 INFO exited: userconf (exit status 0; not expected)
2014-11-01 18:22:47,587 CRIT reaped unknown pid 85)
2014-11-01 18:22:50,591 INFO spawned: 'rserver' with pid 114
2014-11-01 18:22:50,593 INFO spawned: 'userconf' with pid 115
2014-11-01 18:22:50,601 INFO exited: rserver (exit status 0; not expected)
2014-11-01 18:22:50,603 INFO gave up: rserver entered FATAL state, too many start retries too quickly
2014-11-01 18:22:50,676 INFO exited: userconf (exit status 0; not expected)
2014-11-01 18:22:51,123 INFO gave up: userconf entered FATAL state, too many start retries too quickly
2014-11-01 18:22:51,123 CRIT reaped unknown pid 117)

[eddelbuettel]

So maybe we should retittle: "cannot launch iff mounting current home directory as different user's home directory within Docker"

[tshauck]

Hmmm... not sure if that's the case though (or maybe I'm not understanding).

$ docker run -d -p 8787:8787 -v /home/thauck:/home/thauck -e USER=thauck -e PASSWORD=test rocker/rstudio gives me the same error.

I'll update the title to reflect the mounting issue though.

[cboettig]

Trent,

Can you try linking to the home directory on the container of the user you
are logging in as instead of /home/rstudio?

---

Carl Boettiger
http://carlboettiger.info

sent from mobile device; my apologies for any terseness or typos
On Nov 1, 2014 11:34 AM, "Dirk Eddelbuettel" [email protected]
wrote:

So maybe we should retittle: "cannot launch iff mounting current home
directory as different user's home directory within Docker"

—
Reply to this email directly or view it on GitHub
#71 (comment).

[tshauck]

Hi,

See the comment made concurrently to yours.

Hmmm... not sure if that's the case though (or maybe I'm not understanding).
$ docker run -d -p 8787:8787 -v /home/thauck:/home/thauck -e USER=thauck -e PASSWORD=test rocker/rstudio gives me the same error.
I'll update the title to reflect the mounting issue though.

[eddelbuettel]

Names are one thing, uids are another. Carl has fought that battle for a bit. I would probably stay away from mapping all of $HOME.

[tshauck]

@eddelbuettel Stay way from mapping all of $HOME from the host side or the container side? If you could provide an example that'd be great. I tried docker run -d -p 8787:8787 -v $(pwd):/home/$USER/$(basename "$PWD") -e USER=$USER rocker/rstudio from the wiki after having created and cded into /home/thauck/test.

[eddelbuettel]

There are a bazillion dot files below ~, so you risk a conflict. When I want to work on a particular project, say a github repo foo, I just do -v /home/edd/git/foo:/opt/foo and can access foo without issue.

[tshauck]

Ok, that seems to resolve it, though seems wonky that it doesn't work for home. Thank you.

[cboettig]

@tshauck

Hmm,

docker run -d -p 8787:8787 -v /home/thauck:/home/thauck -e USER=thauck -e PASSWORD=test rocker/rstudio

Works just fine for me. I suspect you're using an older version of the image. Can you try docker pull rocker/rstudio to update? If it doesn't work, let me know your container version. I have 7c30474e948c. (you can see the history with docker history rocker/rstudio)

[tshauck]

Just for posterity, this problem seems solved. Thanks for the help.

[santoshshanmukh]

Hi Carl, I am facing the same issue. I am trying to setup rocker/ropensci with boot2docker on windows 7 64-bit. I pulled the image 2073240ffe9b created 8 hours ago.
I started up ropensci with the command:
"docker run -dp 8787:8787 rocker/ropensci"
I am able to access the server at http://192.168.59.103:8787/ and am shown the login
However post login with rstudio/rstudio I get a "RStudio initialization error: Unable to connect to service"
I tried the following as well:
"docker run -d -p 8787:8787 -v /home/ssantosh:/home/ssantosh -e USER=rstudio -e PASSWORD=rstudio rocker/ropensci"
This is what I get in the container logs:
docker@boot2docker:/home/ssantosh$ docker logs --tail=all a7f8722a8275
2015-04-14 07:50:20,090 CRIT Supervisor running as root (no user in config file)
2015-04-14 07:50:20,092 INFO supervisord started with pid 1
2015-04-14 07:50:21,096 INFO spawned: 'rserver' with pid 7
2015-04-14 07:50:21,099 INFO spawned: 'userconf' with pid 8
2015-04-14 07:50:21,114 INFO success: userconf entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2015-04-14 07:50:21,114 INFO exited: rserver (exit status 0; not expected)
2015-04-14 07:50:21,262 INFO exited: userconf (exit status 0; expected)
2015-04-14 07:50:22,266 INFO spawned: 'rserver' with pid 43
2015-04-14 07:50:22,277 INFO exited: rserver (exit status 0; not expected)
2015-04-14 07:50:22,882 CRIT reaped unknown pid 44)
2015-04-14 07:50:24,891 INFO spawned: 'rserver' with pid 63
2015-04-14 07:50:24,902 INFO exited: rserver (exit status 0; not expected)
2015-04-14 07:50:25,484 CRIT reaped unknown pid 64)
2015-04-14 07:50:28,509 INFO spawned: 'rserver' with pid 83
2015-04-14 07:50:28,527 INFO exited: rserver (exit status 0; not expected)
2015-04-14 07:50:29,110 INFO gave up: rserver entered FATAL state, too many start retries too quickly
2015-04-14 07:50:29,110 CRIT reaped unknown pid 84)
docker@boot2docker:/home/ssantosh$

[flaviobarros]

Same issue as santoshshanmukh.

I can see the login screen but unable to connect.

My logs:

2015-04-14 13:58:09,903 CRIT Supervisor running as root (no user in config file)
2015-04-14 13:58:09,905 INFO supervisord started with pid 1
2015-04-14 13:58:10,908 INFO spawned: 'rserver' with pid 13
2015-04-14 13:58:10,910 INFO spawned: 'userconf' with pid 14
2015-04-14 13:58:10,929 INFO success: userconf entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2015-04-14 13:58:10,932 INFO exited: rserver (exit status 0; not expected)
2015-04-14 13:58:11,202 INFO exited: userconf (exit status 0; expected)
2015-04-14 13:58:12,205 INFO spawned: 'rserver' with pid 49
2015-04-14 13:58:12,230 INFO exited: rserver (exit status 0; not expected)
2015-04-14 13:58:12,981 CRIT reaped unknown pid 50)
2015-04-14 13:58:14,986 INFO spawned: 'rserver' with pid 69
2015-04-14 13:58:15,009 INFO exited: rserver (exit status 0; not expected)
2015-04-14 13:58:15,717 CRIT reaped unknown pid 70)
2015-04-14 13:58:18,722 INFO spawned: 'rserver' with pid 89
2015-04-14 13:58:18,744 INFO exited: rserver (exit status 0; not expected)
2015-04-14 13:58:19,595 INFO gave up: rserver entered FATAL state, too many start retries too quickly
2015-04-14 13:58:19,595 CRIT reaped unknown pid 90)

[santoshshanmukh]

I removed the rocker/ropensci image, and installed rocker/hadleyverse instead now.
I am able to start up the service and access the same.

[flaviobarros]

My problem was the docker version. Was outdated.