cc @yifan-gu @aaronlevy

Would vote for something like a rkt kill(#1496)
to stop the pod in a double fork mode. I'd like to defer the API service being root. cc @vcaputo @jonboulle

But we can do a systemd mode first. This should help clean up the kubelet/rkt code as well.

@yifan-gu Agreed, I want non-root API service too. Maybe it is two different things.

I am actively looking for such library. I was in the rkt community sync, where I learned gRPC is not an option because it is not intended (i dont know why? ), but if cli + systemd mode is preferred way to go, then be it, but having this in a go library be easier to maintain and upgrade across the schedulers, builders and all the tools to come. If someone is working on this, I can help testing/bug fixing, if not and you folks are willing to take such contribution, I can work on extracting bits from the kubernetes/nomad driver, acbuild etc.

@ranjib SGTM. Currently I am not able to work on that yet. Feel free to hack on it, patches are definitely welcome :)

Captured the discussion today from the rkt/appc sync.
Currently, the rkt shell out from kubelet include:
Rkt fetch
Rkt image rm
Rkt prepare
Rkt enter
Rkt run (Not necessary shelled out by kubelet, it's the value of the ExecStart int the systemd unit generated by kubelet)
Rkt gc

Journalctl -m (get logs) #2041

Other things that require kubelet to shell out:
Systemctl reset-failed (in garbage collection, should be able to be replaced by dbus.ResetFailedUnit() https://godoc.org/github.com/coreos/go-systemd/dbus#Conn.ResetFailedUnit)
Systemctl --version @philips I didn't find anything in go-systemd to get the version?

cc @tmrts