From owner-freebsd-virtualization@freebsd.org Wed Jun 1 16:31:22 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 67DFDB61B32 for ; Wed, 1 Jun 2016 16:31:22 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::4]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4CFFE1D07 for ; Wed, 1 Jun 2016 16:31:22 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (localhost [127.0.0.1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.nomadlogic.org (Postfix) with ESMTPS id 3FD7D125EE5 for ; Wed, 1 Jun 2016 09:31:21 -0700 (PDT) Received: from [192.168.41.105] (unknown [72.34.113.100]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.nomadlogic.org (Postfix) with ESMTPSA id 38A3D125EBA for ; Wed, 1 Jun 2016 09:31:21 -0700 (PDT) Subject: Re: Running FreeBSD docker images on non-FreeBSD hosts To: freebsd-virtualization@freebsd.org References: From: Pete Wright Message-ID: <94b39ea0-5b80-6d7b-044c-2810d3026761@nomadlogic.org> Date: Wed, 1 Jun 2016 09:31:20 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 16:31:22 -0000 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