Closed benmarwick closed 10 years ago
Hmm, haven't seen that before. What does sudo docker ps
show? Just for reference, what platform are you testing on? I don't get the DNS warning, so that probably has something to do with confusing rstudio server but I'm not really sure.
Honestly I'm not sure how to troubleshoot this, might be worth contacting rstudio too and seeing if they have any ideas.
Let's run interactively and see what we can learn:
sudo docker run --rm -p 8787:8787 cboettig/rstudio /bin/bash
This will drop you into a terminal on the docker machine. Note that because we provided a command (/bin/bash) the default command that launches rstudio isn't running. First, let's just see if we can ping the outside world (shouldn't be necessary, but will show evidence of DNS funny behavior):
ping google.com
Does that work? If not, maybe this will help resolve your issue: http://askubuntu.com/questions/475764/docker-io-dns-doesnt-work-its-trying-to-use-8-8-8-8
You're probably better off googling, but let's just see if we can get more information: Launch the supervisor daemon in the background:
/usr/bin/supervisord &
You should see some console stuff, may include error messages but that seems okay (e.g. still works for me). If things were running successfully you should be able to login at localhost:8787. If you do top
, you should at least be able to verify that rserver is now running (under rstudio user). (I'm guessing it is because something knows to look for auth-sign-in when you go to 8787)
I guess we can also check that rstudio installed the authentication page. do cd /usr/lib/rstudio-server/www/templates
and you should see (ls
) a file called encrypted-sign-in.htm
. That's the page it's looking for...
You should also be able to confirm that you can at least run R in console mode from here...
Thanks for testing this and for the bug report.
Thanks very much for your detailed reply. I'm on Ubuntu 14.04 here, and I can't get to a terminal in the container.
However, I've had more success with boot2docker and got both your rstudio and ropensci containers working fine with that.
So I think this Ubuntu problem might be something beyond the dockerfiles, etc. in this repo and more to do with something specific my system, so I'll consider this closed, and keep tinkering away. Thanks again for taking the time to help with diagnostics.
Hmm, I'm on Ubuntu 14.04 too. What version of docker / install method did you use? I find that one line curl script works well to get the latest version.
So
docker run -it cboettig/rstudio /bin/bash
Doesn't bring you into the container?
Carl Boettiger http://carlboettiger.info
sent from mobile device; my apologies for any terseness or typos On Aug 29, 2014 1:09 AM, "Ben Marwick" notifications@github.com wrote:
Thanks very much for your detailed reply. I'm on Ubuntu 14.04 here, and I can't get to a terminal in the container.
However, I've had more success with boot2docker and got both your rstudio and ropensci containers working fine with that.
So I think this Ubuntu problem might be something beyond the dockerfiles, etc. in this repo and more to do with something specific my system, so I'll consider this closed, and keep tinkering away. Thanks again for taking the time to help with diagnostics.
— Reply to this email directly or view it on GitHub https://github.com/ropensci/docker/issues/1#issuecomment-53848423.
As part of the troubleshooting I'm afraid I've reset the network adapter on my Ubuntu machine (which I was accessing remotely) and can't access it at the moment. It'll take me a few days to get that back to normal. In the meantime, I've made progress on boot2docker, as noted in https://github.com/ropensci/docker/issues/3
oh dear, didn't realize you were running on a remote ubuntu machine. fwiw, I've found testing on a tiny digitalocean.org droplet ($5 / month) to be really easy. You get ubuntu 14.04 with docker installed out of the box, and a fast internet connection for downloading docker images.
On Fri, Aug 29, 2014 at 12:26 PM, Ben Marwick notifications@github.com wrote:
As part of the troubleshooting I'm afraid I've reset the network adapted on my Ubuntu machine (which I was accessing remotely) and can't access it at the moment. It'll take me a few days to get that back to normal. In the meantime, I've made progress on boot2docker, as noted in #3 https://github.com/ropensci/docker/issues/3
— Reply to this email directly or view it on GitHub https://github.com/ropensci/docker/issues/1#issuecomment-53919816.
Carl Boettiger UC Santa Cruz http://carlboettiger.info/
@benmarwick Okay, I've been able to reproduce the /auth-sign-in not found
error exactly by testing on an older version of Docker (0.9.1
in my case; which is the version available in the 14.04 repositories; (Dirk confirmed the same problem running on Debian with 1.0.1). For future reference at least, consider upgrading to Docker >= 1.2. They have a nice one-line install script for this on the docker site: https://docs.docker.com/installation/ubuntulinux/
Thanks for the follow-up, that works perfectly on my Lubuntu 14.04 VM (on windows host), but not on my Ubuntu desktop. I'm putting that down to an obscure misconfiguration of the desktop that is probably unique to that machine and not worth pursuing further here (it's overdue for updates).
In case anyone else is following along (and for the benefit of my future self), this is the one-liner to install the lastest version of docker: curl -sSL https://get.docker.io/ubuntu/ | sudo sh
This is a great jump-start to docker, thanks. I'm using Ubuntu 14.04 and installed docker using these instructions: http://docs.docker.com/installation/ubuntulinux/ then tried
sudo docker run -d -p 8787:8787 cboettig/rstudio
which gives me a warning:
and at http://localhost:8787/ I see
When I try
docker run --rm -i -t -p 80:80 nginx
(as a test of the exposed port) I get the same warning, but when I point my browser to localhost, I seeWhich suggest the port forwarding seems to be fine. Any tips on how to proceed? Thanks again.