This repository has been archived by the owner on Nov 8, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 8
Troubleshooting
jasercion edited this page May 30, 2018
·
12 revisions
Accumulate problems and solutions here.
- There are no man pages. There never will be, this is an artifact of the base centos container used. They removed manpages and I haven't figured out how to get them back.
- X11 forwarding does not work properly in XQuartz 2.7.9 This is a known bug that was fixed in subsequent versions, so as a first step users should update their version to 2.7.11+ . If you need to remain on 2.7.9 this patch will fix the issue:
- As root, edit the file
/opt/X11/bin/startx
- insert after line 107:
else defaultserverargs="$defaultserverargs -listen tcp"
- Save the file and exit
- Kill XQuartz
xhost + 127.0.0.1
- Create a new container and launch an xwindow, like xclock.
- As root, edit the file
- If you can't access the Jupyter notebook via the token generated by the NotebookApp:
- If you are running Docker For Windows, open a Windows Powershell terminal and run
ipconfig
. Note the IP address under the headingEthernet adapter vEthernet (DockerNAT)
. You can also do this when calling the notebook by using the ip flag in the call (i.e.notebook --ip <Your.DockerNAT.IP.Address>
) - If you are running Docker Toolbox, run
docker-machine ip
in the terminal and note the IP address provided. - Change the IP address in front of port 8888 in the token string (should be 0.0.0.0) to the IP address determined above. Reload the page and the Notebook should appear.
- If you are running Docker For Windows, open a Windows Powershell terminal and run
- If you are using the Docker terminal to interact with the container you wont be able to pass the ^Z signal (control-z) to suspend the Jupyter Notebook. To run it in the background use the command
notebook &
. To retrieve your cursor hit enter.
I'm a Fermi in a bottle, baby. Gotta docker run
me the right way.