From owner-freebsd-virtualization@freebsd.org Fri Feb 1 19:49:45 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 6B7FB14BED03 for ; Fri, 1 Feb 2019 19:49:45 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [140.82.23.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.nomadlogic.org", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3AC7376BC3 for ; Fri, 1 Feb 2019 19:49:43 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from duke.gem.co (cpe-76-175-75-27.socal.res.rr.com [76.175.75.27]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 2b1f805b TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Fri, 1 Feb 2019 11:49:36 -0800 (PST) Subject: Re: The status of docker To: Grzegorz Junka , Mark Blackman Cc: Stefan Bethke , freebsd-virtualization@freebsd.org References: <089e330d-2761-2440-3b7f-dd22e9088af5@gjunka.com> <929CF558-E8CC-4F7D-9C30-DDD63C17861D@lassitu.de> <94964BDE-7B14-424B-88A5-4D8F4A9AAC56@exonetric.com> <83736f61-abe9-d85f-a782-1b684808678c@gjunka.com> From: Pete Wright Message-ID: <11fa9f16-0745-c86e-4820-fd9349b4d1ef@nomadlogic.org> Date: Fri, 1 Feb 2019 11:49:36 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0 MIME-Version: 1.0 In-Reply-To: <83736f61-abe9-d85f-a782-1b684808678c@gjunka.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 3AC7376BC3 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of pete@nomadlogic.org designates 140.82.23.70 as permitted sender) smtp.mailfrom=pete@nomadlogic.org X-Spamd-Result: default: False [-5.56 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[27.75.175.76.zen.spamhaus.org : 127.0.0.10]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; FROM_HAS_DN(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[nomadlogic.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[mail.nomadlogic.org]; NEURAL_HAM_SHORT(-0.81)[-0.810,0]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; IP_SCORE(-2.44)[ip: (-8.82), ipnet: 140.82.16.0/21(-4.41), asn: 20473(1.09), country: US(-0.07)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:20473, ipnet:140.82.16.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(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: Fri, 01 Feb 2019 19:49:45 -0000 On 2/1/19 11:39 AM, Grzegorz Junka wrote: > On 31/01/2019 07:50, Mark Blackman wrote: >> What problem are you trying to solve with docker? > > There is a misunderstanding. I am not trying to solve any problem. The > team I am working with is using docker during development (by using a > preconfigured container they avoid having to setup a complex backend > system on development/CI machines). I was hoping to use FreeBSD during > the development but it proved difficult. I now have a choice of either > switching to Linux natively (as bhyve didn't help) or to use MacBook > Pro - both supporting docker out of the box. might be worth taking a look at hashicorp Vagrant.  i've used it with success in developer workflows  in the past where most devs were on macOS and we were targeting FreeBSD. https://www.vagrantup.com/intro/index.html https://app.vagrantup.com/freebsd/ IMHO docker on macOS is kinda hacky since you end up running Linux inside virtualbox, then launch docker on those VM's (at least I believe that used to be the case if things have changed).  i also feel like docker is a double edged sword (aside from the fact that it locks you into linux) in that most people don't do a good job tracking dependencies or actually apply updates/patches to base docker images. i feel like hashicorp did a pretty good in addressing the need to simplify developer workflows between their workstations and eventual target production environments, while also avoiding a lot of the issues that docker has managed to create. -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA