Collin,

Like Peter mentioned, open-vm-tools are not limited to desktop operations. In 
fact, we have split the package into two: open-vm-tools and 
open-vm-tools-desktop.

open-vm-tools is the non-desktop piece. The main service it contains vmtoolsd 
exits immediately if not running on VMware platform.

I need to explore the privileged container approach, but I would also like to 
learn about the technical downsides of including the package in the image 
itself.

Thanks,
Ravindra

-----Original Message-----
From: cloud-boun...@lists.fedoraproject.org 
[mailto:cloud-boun...@lists.fedoraproject.org] On Behalf Of Colin Walters
Sent: Monday, November 24, 2014 8:46 AM
To: cloud@lists.fedoraproject.org
Subject: Re: Adding open-vm-tools package to Fedora Atomic



On Mon, Nov 24, 2014, at 11:09 AM, Peter Robinson wrote:

> It needs some fairly low level "HW" access, not sure how that would 
> work containerised.

If you "docker run --privileged", the container has total access to the host, 
it's no different from any other process running as root.  Try it:

# docker run -ti --privileged -v /:/sysroot centos ls /dev 
_______________________________________________
cloud mailing list
cloud@lists.fedoraproject.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__admin.fedoraproject.org_mailman_listinfo_cloud&d=AAIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=XKRtw3xpbldWU2ByNvo8Foy3TejVp9MFbxmUOOiwqic&m=R98GD8uOST2uyLgm1rjQDvUAZagugIyzd2_4-xgZy-A&s=WGm0MBICoJeRUxRaIt0I5OHH20y8KL8550lB1mx3uD4&e=
Fedora Code of Conduct: 
https://urldefense.proofpoint.com/v2/url?u=http-3A__fedoraproject.org_code-2Dof-2Dconduct&d=AAIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=XKRtw3xpbldWU2ByNvo8Foy3TejVp9MFbxmUOOiwqic&m=R98GD8uOST2uyLgm1rjQDvUAZagugIyzd2_4-xgZy-A&s=txqk0vGGAMgxZniHVkM4iEbQeARfZogWHwuu5SRs1es&e=
 
_______________________________________________
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Reply via email to