Date: Tue, 29 Jan 2019 21:56:37 -0500 From: Paul Kraus <paul@kraus-haus.org> To: David Powers via freebsd-virtualization <freebsd-virtualization@freebsd.org> Subject: Re: The status of docker Message-ID: <4E30C2DA-0CF1-48EF-B1BD-379E5C02D8C8@kraus-haus.org> In-Reply-To: <FE466DD8-8FF9-43B4-8D5E-1AF8FEEE798F@punkt.de> References: <089e330d-2761-2440-3b7f-dd22e9088af5@gjunka.com> <9A01020A-7CC6-4893-A425-11A7BF736F4E@ultra-secure.de> <42f59b63-fdc7-306f-d836-83533741a86c@FreeBSD.org> <CAG=rPVfTZnYc6%2BDjtk0SjkqijJQh6uA1G9VWEBsYy4aDYvYEgQ@mail.gmail.com> <CC0F6FB5-7939-4586-86DD-B5548E0043C3@punkt.de> <5c926314-adce-dba1-f5ce-2fda35e1aeba@gjunka.com> <FDDC8A58-8AD3-4D07-B0B3-0BDFA214ABA0@punkt.de> <7A86028D-C413-4063-84D8-5AB985EAD2A0@kraus-haus.org> <FE466DD8-8FF9-43B4-8D5E-1AF8FEEE798F@punkt.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 28, 2019, at 2:40 AM, Patrick M. Hausen <hausen@punkt.de> wrote: >=20 > Good morning, >=20 >> Am 28.01.2019 um 03:53 schrieb Paul Kraus <paul@kraus-haus.org>: >> (Open)Solaris already had Linux Brand zones, which I=E2=80=99m sure = helped get there much faster. >> They could already run Linux (user space) in a Zone. >=20 > Yes, but how did they get there? Is there some technical reason > why Linux branded zones are =E2=80=9Eso far ahead=E2=80=9C of = FreeBSD=E2=80=99s Linux > ABI that they can run native Docker images while FreeBSD can=E2=80=99t? >=20 > Or is it just a matter of money and manpower invested? May be. Solaris introduced Containers and Zones in Solaris 10 and over = the life of Solaris 10 added new features. I suspect Linux Branded Zones = was developed along side Solaris Branded Zones (which let you run a = different version of Solaris in a Zone), but Sun was paying for the = development effort. All that was over 10 years ago now and the memory is = not as clear as it was then. Joyent also pays people to develop Illumos / SmartOS.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E30C2DA-0CF1-48EF-B1BD-379E5C02D8C8>