Date: Wed, 1 Jun 2016 09:31:20 -0700 From: Pete Wright <pete@nomadlogic.org> To: freebsd-virtualization@freebsd.org Subject: Re: Running FreeBSD docker images on non-FreeBSD hosts Message-ID: <94b39ea0-5b80-6d7b-044c-2810d3026761@nomadlogic.org> In-Reply-To: <CA%2BMCM4s%2BEFcbNV=TaV1Ca_gwFONgDnGEm8p%2BD5eUGC2trX=_-A@mail.gmail.com> References: <CA%2BMCM4v308E8iOzP9TCo57PO2ZqriD%2BevYh9nt6XWvLP%2BWmAUA@mail.gmail.com> <d1475a4a-97f9-ae4e-7ddb-4716e3f58427@pix.net> <CA%2BMCM4s%2BEFcbNV=TaV1Ca_gwFONgDnGEm8p%2BD5eUGC2trX=_-A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 co-workers through that much hell to test out freebsd. having worked on docker (and before that other linux jail-like systems) i never understood the thought process that forces everyone to try to fit all use-cases under one umbrella like this. if you have some workflow that is totally docker depedent then just run freebsd+docker and be done with it. you'll have some linux docker nodes, and some freebsd docker nodes and your on your way. or as mentioned earlier - there are all sorts of para-virtualization technologies that allow one to run freebsd ontop of a linux (or mac) hypervisor. the benefit with either of these approaches is that you remove about 50 hoops and support headaches and probably learn a bit more about how to manage heterogeneous environments along the way. -pete -- Pete Wright pete@nomadlogic.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?94b39ea0-5b80-6d7b-044c-2810d3026761>