Date: Thu, 2 Jun 2016 16:50:19 -0400 From: Jeff Terrell <jeff@altometrics.com> To: freebsd-virtualization@freebsd.org Subject: Re: Running FreeBSD docker images on non-FreeBSD hosts Message-ID: <CA%2BMCM4theEe5bRX1d9O-B6x9DjYHPTozXv4nOxQY-hMydrTC7w@mail.gmail.com> In-Reply-To: <94b39ea0-5b80-6d7b-044c-2810d3026761@nomadlogic.org> 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> <94b39ea0-5b80-6d7b-044c-2810d3026761@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 1, 2016 at 12:31 PM, Pete Wright <pete@nomadlogic.org> 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 for the challenge. (Seriously.) I don't want to add pain to myself and others needlessly. :-) > 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 t= ry > 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 remo= ve > about 50 hoops and support headaches and probably learn a bit more about = how > to manage heterogeneous environments along the way. I think these are great points. And if it were up to me, I can imagine this would be a better approach in many respects. But alas, this is for a project that I don't control. They've chosen docker, and I'm trying to fit a FreeBSD option in among the mix as painlessly as possible (for them). The fuller details are here, if you're interested. [1] [1] https://github.com/bit3/jsass/issues/40 (Indeed, I don't think this problem really requires virtualization at all. It's just that nobody has solved my problem in a portable language yet. The Java software [2], which I'm using indirectly from the Clojure software [3], doesn't solve the problem directly but instead uses JNA [4] to effectively shell out to a library, libsass.so [5].) [2] https://github.com/bit3/jsass/ [3] https://github.com/deraen/sass4clj [4] https://en.wikipedia.org/wiki/Java_Native_Access [5] http://sass-lang.com/libsass That said, if one did create such a monstrosity as a docker image containing a KVM hypervisor containing a FreeBSD VM=E2=80=94and figured out how to pass commands and mount volumes from docker -> FreeBSD via KVM=E2=80=94that could be a nice "evangelism" move to give the masses who u= se docker a cheap and easy way to try out FreeBSD. Plus, such an image could be used to provide FreeBSD support for other software as well. Maybe I'll add that to my "one of these days" list... --=20 Jeff Terrell, Ph.D. | Chief Technology Officer ALTOMETRICS, Inc. (919) 357-3116 | www.altometrics.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BMCM4theEe5bRX1d9O-B6x9DjYHPTozXv4nOxQY-hMydrTC7w>