Date: Fri, 1 Feb 2019 20:07:30 +0000 From: Mark Blackman <mark@exonetric.com> To: Grzegorz Junka <list1@gjunka.com> Cc: Stefan Bethke <stb@lassitu.de>, freebsd-virtualization@freebsd.org Subject: Re: The status of docker Message-ID: <088AA858-AA5E-451A-90E9-016153C685C6@exonetric.com> In-Reply-To: <83736f61-abe9-d85f-a782-1b684808678c@gjunka.com> References: <089e330d-2761-2440-3b7f-dd22e9088af5@gjunka.com> <929CF558-E8CC-4F7D-9C30-DDD63C17861D@lassitu.de> <a63ae2e5-28ba-5946-a8b6-28d29007ea7a@gjunka.com> <94964BDE-7B14-424B-88A5-4D8F4A9AAC56@exonetric.com> <83736f61-abe9-d85f-a782-1b684808678c@gjunka.com>
index | next in thread | previous in thread | raw e-mail
> On 1 Feb 2019, at 19:39, Grzegorz Junka <list1@gjunka.com> 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. - Markhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?088AA858-AA5E-451A-90E9-016153C685C6>