On 11/22/2014 06:20 AM, Haïkel wrote:
You may use Fedora Atomic as an alternative to boot2docker, though it
won't be as small as boot2docker.
I think there's some additional tooling around boot2docker, but I have
to admit I haven't used it + don't know enough about it. Maybe something
to test
I've used Boot2Docker - it's point, click and ship Docker hosting for
Windows or MacOS X and it bundles the open-source piece of VirtualBox to
get that done. I haven't used it on a Mac but on Windows you download an
installer and run it. It installs VirtualBox, Windows MSYS Git and the
Boot2Docker
Hi Ravindra,
At the moment, we do not have a formal process for this. The problem is
further compounded by the fact that there is only one tree. Meaning that
open-vm-tools would end up even on other deployment targets such as bare
metal, AWS/GCE, etc.
At a high level, we are trying to coalesce
On Mon, Nov 24, 2014 at 3:38 PM, Colin Walters walt...@verbum.org wrote:
Hi Ravindra,
At the moment, we do not have a formal process for this. The problem is
further compounded by the fact that there is only one tree. Meaning that
open-vm-tools would end up even on other deployment targets
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:
#
:34 AM
To: Fedora Cloud SIG
Subject: Re: Adding open-vm-tools package to Fedora Atomic
Great - is there a *technical* (meaning non-policy) reason why Fedora's version
of open-vm-tools doesn't support mounting host files in the guest? VMware does
such a terrible job at tracking changes in the kernel
...@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
2014-11-22 1:26 GMT+01:00 M. Edward (Ed) Borasky zn...@znmeb.net:
You'd need to reformat them to vmdk with 'qemu-img convert' first, I think.
I got the Koji image to work on Windows 8.1 Client Hyper-V by using
'qemu-img convert' to convert it from qcow2 to vhdx.
On a related note, is there a
Hi all,
I'm the maintainer for open-vm-tools package in Fedora.
For the benefit of Fedora Atomic users on VMware platform, I would like to add
open-vm-tools package to Fedora Atomic.
Could somebody please advise/help me with the process involved to get
open-vm-tools package in Fedora Atomic?
Great - is there a *technical* (meaning non-policy) reason why Fedora's
version of open-vm-tools doesn't support mounting host files in the guest?
VMware does such a terrible job at tracking changes in the kernel source
that I've given up on using it. And why is open-vm-tools installed by
default
On 11/21/2014 01:51 PM, Ravindra Kumar wrote:
Could somebody please advise/help me with the process involved to get
open-vm-tools package in Fedora Atomic?
Silly question - do the qcow/etc images we're producing now run on
VMware? I haven't tried importing them to anything VMware...
Best,
jzb
You'd need to reformat them to vmdk with 'qemu-img convert' first, I think.
I got the Koji image to work on Windows 8.1 Client Hyper-V by using
'qemu-img convert' to convert it from qcow2 to vhdx.
On a related note, is there a plan to build boot2atomic? Like
Boot2Docker, only Atomic instead of
12 matches
Mail list logo