From owner-freebsd-virtualization@freebsd.org Fri Jan 29 11:48:29 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 E7B73A72302 for ; Fri, 29 Jan 2016 11:48:28 +0000 (UTC) (envelope-from doublef.mobile@gmail.com) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 84A251E97 for ; Fri, 29 Jan 2016 11:48:28 +0000 (UTC) (envelope-from doublef.mobile@gmail.com) Received: by mail-wm0-x22f.google.com with SMTP id 128so49412448wmz.1 for ; Fri, 29 Jan 2016 03:48:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc:content-type; bh=ZHRM2AbhvL304XgNXkHds4g5M4/TUb3DpaltFkKwJH4=; b=YXP9xTZ7/9CX8mrMeOsirZ3Q53MT3YL0/KB7xJB5BKhA49K0DkTOkVI0CMiWZ5tGFC DM8/7W9rq4caTUuyKXfEMi7USBspFdd2vQvYSXykhbiuGRkmLKp1vp+xSdpC/J4fx5cR wYmBdeohKAc9pgkj6iJoClYCOCZgmbMR5F9739P0kVjORNeM1UyYiK6YQGpvfHEs8hZH fIBwZB+YO7CKLs1DnKfn6eORMUwaN4PWS1S72a2fxHA6SDB/28ipQdQoTTe6cXGZTeFR BtB/ZkRE/TEkrbc87m154BtwL29LCV4cMHOPBSzuBowSwslpVJrHKzz9deIqn0fA59xV H5JQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc :content-type; bh=ZHRM2AbhvL304XgNXkHds4g5M4/TUb3DpaltFkKwJH4=; b=IxAyfMqnfnpU1BF/Ye9bHEIjOxYDt+68o1aBb+WqxIAWxLUcXZuKajQfcXTPYjbmAi S5wZ8NkPJ/MdDgcfwmymEXE3qxA7rjdofXFbzzS49I87DxLq+5CBJ/nMtJ7aFCFaSPzW 8uGYA1odqME/LAJR3iS2p+HnWi+VF8L3MfK8KZox4kR46zKIudI9sz5/vY+LJU5pCumo 1eBLNa9TaOHSX18uZhnXEs0NonH2TuKlkxDZTOkAaVJqSshi9UKrRsWKZza9KwmbJyto l/+YblmT3PdZLzPSHG2Me/vOpAubTw1bXyy4zyVvWys1v77djUDdL51Rm8yGUpLrDQws EGpw== X-Gm-Message-State: AG10YOQRj7sdJMMKuVKc6rNhx9Afe9oB7jj7fIOkIfip+E/OZa8qyLPJzM5qJVsYCyzUO67qfjSVQuXhmj/sNg== X-Received: by 10.194.203.99 with SMTP id kp3mr8295572wjc.3.1454068107096; Fri, 29 Jan 2016 03:48:27 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.93.6 with HTTP; Fri, 29 Jan 2016 03:48:07 -0800 (PST) From: Sergey Zakharchenko Date: Fri, 29 Jan 2016 14:48:07 +0300 Message-ID: Subject: ATTN Docker, Jetpack users (was: Re: Docker on FreeBSD) To: Matthew Veety , Ryan Holt Cc: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 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: Fri, 29 Jan 2016 11:48:29 -0000 Hi Matthew, > What needs to be done with docker to get it running better on FreeBSD? Is > there any place with a list of bugs or a todo list? I would be interested in > getting it working better. It's more like a list of things which work, many things that don't, and a sea of things which 'sorta' work. Mainly because of this one entry in https://github.com/kvasdopil/docker/blob/freebsd-compat/FREEBSD-PORTING.md : >>> volumes - not working It's a small benign-looking entry. Not in bold, not highlighted, hidden deeply from those unaware. Image building doesn't *really* work because of that, because the resolver configuration and hosts file are, like, 'single-file mounts'. So when you do a pkg install in the image-building container, you get no address record. Jumping through some hoops, including custom-generated Dockerfiles (what a crappy file format BTW), can still get things done. You're left with jumping more hoops with adding the volumes when you instantiate and start a container. Problems indicated by kvasdopil: Docker is too much of a moving target and his patches no longer apply to the latest, they change everything all the time (e.g. network config revamping, etc.). That is a valid concern. Should I contribute to the whole thing? Too few people seem to care. My questions are: Is anyone here interested in a patch which improves container-building performance (I'm patching Docker but a similar approach should benefit Jetpack)? Now, is anyone interested and *competent enough* in fixing the volume problem? Oh, and there's the whole port forwarding thing... >>> port forward - ok OK would be native support of a FreeBSD firewall, e.g. PF. Please don't tell me you like the userland proxy. That's partial support, and the container access logs become useless... P.S. Ryan wrote: > I've since moved to Gentoo, ZFS for Linux, and Docker. Works really well. That's exactly the attitude the current state of things provoke. Not blaming you in any way. Docker in general sounds like 'run it anywhere and pray it's the latest 64-bit Ubuntu' :) Best regards, -- DoubleF