Is this a question of discovering the right configuration file that let’s you solve your problem (“I need to set environment variables when this container starts, how do I do that?”)? Or a question of getting all the right packages to play nicely together? Or a third thing?
I think this is at least a two step problem:
how do I launch and configure a VM on cloud hoster X so that it has a docker daemon I can
use
how do I connect to the running notebook/RStudio session on that remote VM from my local computer
Is there a third angle to this? I think we could start to address this with a “Howto” style guide in the documentation. My feeling is that we should find existing tools/guides for question 1 as we can’t maintain docs for all the various cloud hosters ourselves. For question 2 I think the answer is generic so we can add it to the FAQ and a Howto guide. What do you think?
Maybe we should break this thread out into a new topic: “The hard things about using repo2docker” or some such?
Yeah, I think separate app is definitely the way to go. In the same way that mybinder.org is a web service built on repo2docker’s cli, this would be a local gui app built on repo2docker, consuming its api (could be via cli or python).
When dealing with ephemeral cloud resources, pushing to a private registry is probably sensible to include, so you can build once and run several times. I’d almost call this a “mybinder.org, deconstructed” guide. It’s everything Binder does, but taken as more manual steps on your own terms:
request cloud resources
build image with repo2docker (requires installing docker)
store image in a registry for future use (requires registry credentials; docker login being the easiest)
launch a container from the image
connect to the running notebook (might require cloud firewall configuration)
What is the status, support and adoption like for docker-machine these days? It seems like it could be a good way to get a machine that runs dockerd in the cloud and run containers on it.