SvenDowideit

Deliver and release stuf that people actually use. Or work on projects that do.

Delivering value trumps painting every day

"everything" running in a container is pretty much the difference.

RancherOS has a built in Go PID1 that starts a system Docker for the system services, and a user Docker that you then run your apps in.

This also means your console, and user container run time is a switchable container image.

Yep, RancherOS works on ARM, and we're building out our build and test infra.

Mostly, we're all working, cribbing off each other to get to our individual goals.

only if you're expecting containers to somehow be a unicorn that lets you give people you don't know have your root password. :)

will you be adding it to CCAN (the C code archive, in a similar spirit to Perl's CPAN)?

see http://ccodearchive.net/

almost,

LXC starts as a general purpose Linux container with everything built in, and adds more isolation as development continues

ZeroVM starts with no general purpose Linux, and will add support as development continues

ie, LXC will work with what you have now, ZeroVM will eventually work with what you have now, but shims will have to be developed for everything, either in your code, or in ZeroVm's

IMO the future endpoint will have similar functionalty in both projects, but LXC will see more testing and use /now/