> Am 02.06.2016 um 22:50 schrieb Jeff Terrell :
>
>
> That said, if one did create such a monstrosity as a docker image
> containing a KVM hypervisor containing a FreeBSD VM
A guy at work ran a chef-server on Ubuntu in a headless VirtualBox in a Solaris
10 Zone.
He really liked Solaris.
_
On Wed, Jun 1, 2016 at 12:31 PM, Pete Wright wrote:
>> So it looks like, if I'm committed to docker, I could run FreeBSD
>> inside a KVM inside a container on Linux. Then others who might be
>> interested in FreeBSD could play around with it on their Linux hosts
>> via docker.
>
> why?!?
Thanks f
On 06/01/2016 09:04 AM, Jeff Terrell wrote:
So it looks like, if I'm committed to docker, I could run FreeBSD
inside a KVM inside a container on Linux. Then others who might be
interested in FreeBSD could play around with it on their Linux hosts
via docker.
why?!?
why put yourself and your
On Tue, May 31, 2016 at 6:08 PM, Kurt Lidl wrote:
> What isn't really explained in so many words -- the container uses the
> system calls from the hosting computer to evaluate anything that it
> needs the "kernel" to do. So your "FreeBSD docker" image, when run on
> a Linux machine, is attempting
I'm acquainted with docker, but I don't know enough to understand
why an image would run in a container on one OS but not in a
container on another OS. I thought the whole point of docker was
that, assuming the image worked at all, it worked regardless of which
host you used. So that's an incident
On 2016-05-31 17:02, Jeff Terrell wrote:
To work around the current inability to mount volumes in FreeBSD docker,
I'd like to use a FreeBSD docker image on a non-FreeBSD host. Then I can
both run FreeBSD in a docker container and mount a volume in the container,
both of which are necessary for my