freenode/#clasp - IRC Chatlog
Search
14:50:36
SAL9000
Do you have a slimmer Docker image (w/o the CANDO & Jupyter stuff)? I want to try using your ASTMatcher bindings to generate CM-C++ glue code.
15:40:16
drmeister
The drmeister/cando is the slimmest docker image I've generated. It's about 2.8GB - that's down from about 9GB when I build everything.
15:41:20
drmeister
It builds a full Cando build environment and then builds a slim docker image with minimal dependencies and copies the clasp/cando executable and support files into it.
15:42:21
drmeister
If you want something more tailored to ASTMatcher work - tell me - we can tune a docker image to that.
15:42:33
SAL9000
Right. I didn't mean that it was too big in terms of disk space -- I meant that you autostart Jupyter et.al.
15:44:03
drmeister
That docker image starts a jupyter notebook server from within which you can start a swank server and communicate with the same Common Lisp instance in the jupyter notebook.
15:44:26
drmeister
You might want to think about that. You could develop code with slime/swank and then users could use the jupyter notebook interface.
15:45:47
SAL9000
ideally, the docker image would be set up in such a way that I can load up SLIME in the CM-specific emacs, but that's probably a bit much
15:46:46
SAL9000
NB: I have to use Docker Machine, since I'm using VirtualBox in parallel with Docker
15:46:50
drmeister
Previous versions of the docker image started a swank server rather than a jupyter notebook server.
15:48:35
drmeister
I have two undergraduates who have Windows machines. They are running the Docker toolbox thing.
15:50:09
drmeister
With a few hours work I could create a docker-compose.yml entry that would build a standalone clasp that runs a swank server and you mount a Windows directory within it.
15:51:18
drmeister
We are mounting three host directories into the drmeister/cando container - that turns it into a kick-ass Cando development environment where we edit code in the local file system and evaluate it into swank server running in the docker container.
15:51:41
drmeister
The Common Lisp running in the docker container has access to the host file system through mount points.
15:52:11
SAL9000
Long story short -- I have to use Windows for Configura's stuff, but I want to keep easy access to Linux, so I set up VB with disk passthrough
15:54:16
drmeister
For this idea of using a docker containerized clasp to access the ASTMatcher facilities to scrape C++ code - the VB layer looks like it complicates things rather than simplifying them.
15:55:19
SAL9000
since I want to keep using VB, I can't use HyperV, so I can't use Docker for Windows which only works with HyperV
15:55:40
SAL9000
I happen to be using Docker Machine with the VB backend, so there is also a "VB layer" but that's not a hard requirement
15:56:57
SAL9000
if the pro version can play nice with other virt solutions, I'll talk to Goran about forking over for it
15:58:01
drmeister
I don't know much about the different versions other than that they exist. I _think_ the professional version requires the professional version of Windows.
15:58:45
drmeister
And I _think_ the professional version of Windows has more Posix support and so it requires less work on docker's end to support docker.
15:59:14
SAL9000
closest thing to "more POSIX support" I've heard of is WSL, which isn't enough to run docker
16:01:13
drmeister
All I really know is that I spent several hours banging my head against a wall getting Docker CE to work with drmeister/cando and we got it working. In the next couple of days we will be doing it over again with a new drmeister/cando and this idea of mounting multiple directories into the docker container.
16:03:10
SAL9000
instead of taking a week to migrate everything to windows I just keep running my existing setup in VB with disk passthrough