2015-07-08 12:14 GMT+02:00 Michal Fojtik <mfojtik@xxxxxxxxxx>: > No, I mean that when you run the container in cluster (like in > Kubernetes/Atomic/OpenShift) you obviously > don't have "docker top" but you have "kubectl exec" or "oc exec". You don't > know on which node the container > runs and therefore you need to use the "exec" approach. > Ok, that's much less sketchy than supporting SysV initscript installation. To me, it's a matter of Kubernetes not exposing information that is available by the underlying engine. First step would be opening a RFE to kubernetes/OpenShift to make this available. Requiring images to provide ps for this use is a *workaround* Moreover, fixing deps in rolekit would just fix the original issue. That would benefit to people using systemd-networkd (like our cloud images) and wants to use rolekit. H. _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
