From owner-freebsd-virtualization@freebsd.org Fri Feb 1 21:19:31 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 2029D14C0FA6 for ; Fri, 1 Feb 2019 21:19:31 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6289682023 for ; Fri, 1 Feb 2019 21:19:30 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from crayon2.yoonka.com (crayon2.yoonka.com [10.70.7.20]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id x11LJRat074795 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 1 Feb 2019 21:19:27 GMT (envelope-from list1@gjunka.com) Subject: Re: The status of docker To: 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> <088AA858-AA5E-451A-90E9-016153C685C6@exonetric.com> From: Grzegorz Junka Message-ID: <926ad6f2-a901-f5b0-cd1a-03c313f3b85f@gjunka.com> Date: Fri, 1 Feb 2019 21:19:27 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.3.2 MIME-Version: 1.0 In-Reply-To: <088AA858-AA5E-451A-90E9-016153C685C6@exonetric.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-GB-large X-Rspamd-Queue-Id: 6289682023 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of list1@gjunka.com designates 88.98.225.149 as permitted sender) smtp.mailfrom=list1@gjunka.com X-Spamd-Result: default: False [-6.69 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:88.98.225.149]; MX_GOOD(-0.01)[cached: gjunka.com]; NEURAL_HAM_SHORT(-0.74)[-0.737,0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:56478, ipnet:88.98.192.0/18, country:GB]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[gjunka.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(-3.64)[ip: (-9.53), ipnet: 88.98.192.0/18(-4.77), asn: 56478(-3.81), country: GB(-0.09)]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] 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 21:19:31 -0000 On 01/02/2019 20:07, Mark Blackman wrote: > >> On 1 Feb 2019, at 19:39, 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. > In this case, the problem you were trying to solves sounds something like “how do I collaborate with my team who have already chosen docker while sticking with my preferred OS” > > The problem your team was trying to solve was “how do I avoid building a complex backend system on development/CI machines?” > > I do believe there is some value in mimicking docker without actually being docker and jetpack had a go at that. > > - Mark > I don't think the team was trying to solve any problem. They just picked up docker because of fashion, it was proposed by one developer and others just stuck with it as it makes their life easier. But yes, you can see it as such (as you described). Anyway, jetpack is based on Vagrant, uses ansible and Go and is experimental. As I said, I spent one day trying to set it up and it was already too much (they don't pay me for setting up my development environment but for implementing code). I just didn't have time to try other solutions, and jetpack didn't look like something that could be set up quickly (especially that I build my packages, so would need to add the time needed to build Vagrant and missing dependencies to it). However, jetpack has been mentioned here before and I see the code is fairly up to date so might have a go at trying to use it when I find some time. Thanks GrzegorzJ