Yeah. My understanding of Rocket from the original blog post is that they don't have an "API" in the sense the Docker one is described at all. Since Rocket is j

Yeah. My understanding of Rocket from the original blog post is that they don't have an "API" in the sense the Docker one is described at all. Since Rocket is just a container format/runner, there's no client/server relationship to document. You're running an executable on your system just like any other. I'm new to Docker, so maybe there are some big wins surrounding the docker client/server architecture that I'm not realizing. But I already have tools in place to run commands on a remote server -- that's not the problem that I'm looking to Docker to solve. So if Rocket is able to get the containerization aspect working smoothly with fewer moving pieces, I'll count that as a point in its favor. In fairness to Docker, I haven't had too much trouble so far pretending that "docker run" commands without the "-d" flag are just running the process in that PID. So the extra hidden complexity of really running it in another process and piping stdout back hasn't affected me in any negative way either.