From owner-freebsd-virtualization@freebsd.org Sun Jan 27 13:59:51 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 82BA214AD07C for ; Sun, 27 Jan 2019 13:59:51 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2a00:14b0:4200:32e0::1ea]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gilb.zs64.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7CCE26A875 for ; Sun, 27 Jan 2019 13:59:50 +0000 (UTC) (envelope-from stb@lassitu.de) Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id 2F8B920B41F; Sun, 27 Jan 2019 13:59:48 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: The status of docker From: Stefan Bethke In-Reply-To: <089e330d-2761-2440-3b7f-dd22e9088af5@gjunka.com> Date: Sun, 27 Jan 2019 14:59:47 +0100 Cc: freebsd-virtualization@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <929CF558-E8CC-4F7D-9C30-DDD63C17861D@lassitu.de> References: <089e330d-2761-2440-3b7f-dd22e9088af5@gjunka.com> To: Grzegorz Junka X-Mailer: Apple Mail (2.3445.102.3) X-Rspamd-Queue-Id: 7CCE26A875 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of stb@lassitu.de designates 2a00:14b0:4200:32e0::1ea as permitted sender) smtp.mailfrom=stb@lassitu.de X-Spamd-Result: default: False [0.47 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.13)[-0.130,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[lassitu.de]; NEURAL_SPAM_SHORT(0.95)[0.946,0]; NEURAL_HAM_LONG(-0.60)[-0.597,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: gilb.zs64.net]; RCPT_COUNT_TWO(0.00)[2]; IP_SCORE(0.06)[ipnet: 2a00:14b0::/32(0.18), asn: 13135(0.12), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13135, ipnet:2a00:14b0::/32, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 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: Sun, 27 Jan 2019 13:59:51 -0000 Am 19.01.2019 um 15:24 schrieb Grzegorz Junka : >=20 > Hello, does anyone know the current status of docker on FreeBSD? Wiki = https://wiki.freebsd.org/Docker states it's experimental. The last = commit in https://github.com/kvasdopil/docker/tree/freebsd-compat is = also from 2015. >=20 > There in fact are two ports, freebsd-docker (from 2015) and docker = (18.06). What's the difference between them and which one should I use = to run docker images on FreeBSD host? I believe at this point in time, all you can do is have a Linux machine = somewhere (for example, in a local Bhyve VM), and use the Docker command = line client from FreeBSD to manage it. That=E2=80=99s what = sysutils/docker is for. > Has this project been completed and now only needs testing, or has it = been abandoned, or maybe the approach has changed and I am looking in a = wrong place? It looks abandoned, unfortunately. And looking at the entire container = infrastructure, reviving it would require a significant effort. For = example, it most real-life usage scenarios, you want to be able to = manipulate IPFW/PF entries to forward ports from a host interface into a = container, which would require special plugins for Docker, or a = compatibility shim that allows Docker to use iptables APIs/ABIs. Going even further, pretty much everything in the ecosystem (k8s, etc.) = assumes it's running on top of a Linux kernel including a number of = management APIs that are not (completely) emulated on FreeBSD. While I would love to see proper Docker support in FreeBSD, I=E2=80=99m = not sure its even the right thing to aim for. In Docker production = environments, people generally try to pare down the host OS to the = absolute minimum, and at that point, what benefit would you derive from = FreeBSD as a host? Similarly, why would you want to run FreeBSD-ABI containers, = specifically? One of the benefits of the container ecosystem is that = there are many ready-made images you can build on. Having to re-invent = all of this seems of little benefit to me. Just my 2 cents, Stefan --=20 Stefan Bethke Fon +49 151 14070811