News for hackers. Stuff that matters.
Re:Docker's killer feature by kcorbitt on Tuesday December 02, 2014 @07:24PM (#8691074)
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.

Re:Docker's killer feature by perlpimp on Tuesday December 02, 2014 @07:29PM (#8691108)
our team is running containers in boot2docker virtualboxes, rocket does not mention anything about being able to run on OS X visualization layer. so docker compatibility is paramount or a stable boot2docker alternative.
Re:Docker's killer feature by robszumski on Tuesday December 02, 2014 @07:43PM (#8691155)
CoreOS runs on many VM platforms, Vagrant/Virtualbox being one of them. The current CoreOS kernel/userland (and most new kernels and Linux distros) is ready to run Rocket. Is that what you're looking for?

https://coreos.com/docs/running-coreos/platforms/vagrant/

(CoreOS employee)

Re:Docker's killer feature by wmf on Tuesday December 02, 2014 @08:04PM (#8691232)
ssh virtualbox rkt run? Personally, I find using docker to talk to a remote dockerd kind of unintuitive.