On 16 January 2016 at 12:07, Kurt Pagani <[email protected]> wrote: >> >> So the notebook option --ip=* makes it work! >> >> wspage@suse:~> docker run -p 443:8888 -t -i nilqed/fricas_jupyter >> jupyter notebook --ip=* --no-browser > > Yes, I always use this option because my "images" are on a server, > however, if you're working locally then it ought go without this. > Admittedly, I've never checked this claim ;) >
As I understanding it, docker assigns ip addresses to containers in the range 172.17.0.x with the host having address 172.17.0.1. These are used to set up the port mappings, e.g. 443:8888. localhost in the container is (usually) assigned 127.0.0.1 by the operating system. So it is important that jupyter notebook be able to listen on ports other than localhost. A couple of other comments about the docker image: 1) It seems that the Jupyter root is set to /. This seems unnatural in general since that exposes the usual linux root directories - although I can understand that it is convenient for now. How should this be handled in the future? Can the Jupyter root be set via the command line when the docker image is started? 2) Apparently the default command shell is /bin/sh when a Jupyter Terminal windows is opened. This seems to cause trouble with the usual history mechanism one expects from bash. It is possible of course to start a bash shell and things then work as usual but I wonder it bash should not be the default? Again, perhaps this can be set from the Jupyter command line? >> >> Thanks again for putting this all together. I am still looking >> forward to getting this into SMC. Can I help push that along? >> > > I'd be glad if you could. At the moment I've no idea how to convince WS > to take the burden of the installation. Or do you think a docker image > will work as well? > I don't think SMC can use docker images. William Stein needs to be able to globally install a Jupyter kernel for FriCAS on SMC. The easier we can make it for him to do that the better - just one command would be ideal. I haven't checked your documentation yet, but is it still necessary to recompile FriCAS to install part of the interface? If this is the case, then perhaps it would be better first to resolve how to get this interface included in the FriCAS distribution. Regards, Bill Page. -- You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/fricas-devel. For more options, visit https://groups.google.com/d/optout.
