Piotr Skamruk

Btw. I'm also interested in that who should be notified on kubernetes side in case of creating new release of cni plugins, as week ago I didn't had this information...

This looks for me as issue better suited for https://github.com/appc/cni @steveeJ what do you think about this?

Right. CNI should only give this information to execution engine (in this case - to `rkt`). How this would be then used by it, in time of application preparation -...

Nice hint to be described in docs, but isn't this too much application specific for now? Most applications (as based on glibc) expects only that there will be correctly configured...

What you mean by "normally"? This looks like you are assuming a glibc based application. Do you know how golang based statically compiled application does name resolving? Hint: there is...

Much cleaner resolution with full support of "legacy" applications. So maybe we could use this as default, if there is no `--dns` option provided and there is listening process on...

Case should be more or less like: - if there is `--dns` flag - use it, else - if there is process bound on udp `127.0.0.53:53` - use `127.0.0.53` like...

Please look on previous comments in this discussion. Statically linked programs in golang do not use glibc nss, and this is why this discussion was going.

I don't have a machine with openvz right now, but as it is already containerization engine, it's really big chance that some host namespaces are not exposed into openvz container....

Looks like host kernel have disabled some particular cgroup subsystems (or even does not have them), or does not expose them into container. Could you give us information which kernel...