Ian Denhardt

Cool, keep me posted. Quoting JJ (2019-01-18 07:51:20) > FYI: nothing too amazing happened so far. There is a base image now. > > Code: [1]https://github.com/JamborJan/Sandstorm-Docker-Base-Image > Image: > [2]https://cloud.docker.com/u/xwrch/repository/docker/xwrch/sandstorm-d...

Started working on these in the base-images directory.

The sandstorm-http-bridge base image is now published on dockerhub. There's an example under `examples/` using it as a base to build a trivial python app (we could probably abstract this...

Great; I look forward to hearing.

Know the feeling; no worries if it doesn't happen.

Yeah, I don't think there's really anything docker can do for us to alleviate the pain points of sandstorm being a fundamentally weird environment to run in. If there were...

The image is actually debian, not Ubuntu. But yeah, the only real hard requirement is that sandstorm is installed in the VM. The stacks themselves are more tied to debian...

My take would be to make the Vagrantfile part of the stack. With `docker-spk` our "stacks" are just vanilla docker images; you put `FROM baseimage` in a Docker file just...

Did you compile it? I don't see that in your command listing. Unlike vagrant-spk, docker-spk is written in a compiled language. See `Building` in the readme.

Would probably be good to ship binaries too; part of why I've delayed is because I want to work out how to make the builds reproducible. I'm a bit uncomfortable...