[IPython-dev] Unable to start Jupityr on Docker using "Quick start" instructions

[roalexan]

The problem with not being able to run 'sudo docker pull jupyter/demo'
appears to have been fixed in Docker 1.0.1. Here's where I am now. I run
these exact steps:

# Create virtual machine
	Virtual Machines>New>Compute>Virtual Machine>From Gallery>Ubuntu>Ubuntu
Server 14.04 LTS
		Password:PASSWORD,Name:HOST,Tier:Standard,Size:A4,
		Add endpoint;name:ipython_nb,protocol:TCP,public port:8000,private
port:9999
# Get Docker
	sudo apt-get -y update
	sudo apt-get -y install docker.io
	sudo ln -sf /usr/bin/docker.io /usr/local/bin/docker
# Get/Start containers
	sudo docker pull jupyter/demo # takes 45 minutes
	export TOKEN=$( head -c 30 /dev/urandom | xxd -p )
	sudo docker run --net=host -d -e CONFIGPROXY_AUTH_TOKEN=$TOKEN
jupyter/configurable-http-proxy --default-target http://127.0.0.1:9999
	sudo docker run --net=host -d -e CONFIGPROXY_AUTH_TOKEN=$TOKEN -v
/var/run/docker.sock:/docker.sock jupyter/tmpnb python orchestrate.py
--cull-timeout=60 --docker-version="1.12" --mem-limit=512m --pool-size=10

When I test from a browser, I see:

	tmpnb
	The server you requested is no longer running or it doesn't exist.
	Starting a new notebook server, just for you...

and then:

	Oh snap!
	It looks like we're full up. Every single container is in use right now!
Try again later and maybe you'll have better luck. Sorry for the
inconvenience!
	If you hang around here for a while, you'll automatically retry in 600
seconds.

Looking at the running Docker containers, I see:

sudo docker ps
CONTAINER ID        IMAGE                                    COMMAND               
CREATED             STATUS              PORTS                       NAMES
d7966e5e8811        jupyter/demo:latest                      "/bin/sh -c
'ipython   42 seconds ago      Up 40 seconds       127.0.0.1:49153->8888/tcp  
compassionate_perlman
f50f981a39af        jupyter/demo:latest                      "/bin/sh -c
'ipython   11 minutes ago      Up 11 minutes       127.0.0.1:49154->8888/tcp  
stupefied_mclean
4e2630ccb2c1        jupyter/demo:latest                      "/bin/sh -c
'ipython   12 minutes ago      Up 11 minutes       127.0.0.1:49155->8888/tcp  
stoic_carson
bad13e2189e7        jupyter/demo:latest                      "/bin/sh -c
'ipython   12 minutes ago      Up 12 minutes       127.0.0.1:49156->8888/tcp  
prickly_elion
09fa0a489f43        jupyter/demo:latest                      "/bin/sh -c
'ipython   12 minutes ago      Up 12 minutes       127.0.0.1:49157->8888/tcp  
condescending_nobel
3a7cc32240e2        jupyter/demo:latest                      "/bin/sh -c
'ipython   13 minutes ago      Up 13 minutes       127.0.0.1:49158->8888/tcp  
hopeful_tesla
4e3f244a023f        jupyter/demo:latest                      "/bin/sh -c
'ipython   13 minutes ago      Up 13 minutes       127.0.0.1:49159->8888/tcp  
angry_bardeen
0a127865e2bc        jupyter/demo:latest                      "/bin/sh -c
'ipython   14 minutes ago      Up 14 minutes       127.0.0.1:49160->8888/tcp  
tender_turing
8f806d6a3c37        jupyter/demo:latest                      "/bin/sh -c
'ipython   14 minutes ago      Up 14 minutes       127.0.0.1:49162->8888/tcp  
berserk_meitner
d4e518665164        jupyter/demo:latest                      "/bin/sh -c
'ipython   47 minutes ago      Up 47 minutes       127.0.0.1:49161->8888/tcp  
sharp_mcclintock
322cdaa75933        jupyter/tmpnb:latest                     python
orchestrate.p   47 minutes ago      Up 47 minutes                                  
berserk_fermat
6d9376d46e54        jupyter/configurable-http-proxy:latest  
configurable-http-pr   54 minutes ago      Up 54 minutes                                  
pensive_tesla

I'm guessing that the browser error is reflecting the fact that there are
already ten containers running, and there is no room for another one? So, I
stopped and removed a couple of them using:

sudo docker stop f50f981a39af
sudo docker stop 4e2630ccb2c1
sudo docker rm f50f981a39af
sudo docker rm 4e2630ccb2c1

and verified that there are now either containers running. However, I still
get the same browser error. Any thoughts on how to get this working?



--
View this message in context: http://python.6.x6.nabble.com/Unable-to-start-Jupityr-on-Docker-using-Quick-start-instructions-tp5075454p5075948.html
Sent from the IPython - Development mailing list archive at Nabble.com.