Date: Fri, 1 Feb 2019 21:07:20 +0000 From: Grzegorz Junka <list1@gjunka.com> To: Pete Wright <pete@nomadlogic.org>, Mark Blackman <mark@exonetric.com> Cc: Stefan Bethke <stb@lassitu.de>, freebsd-virtualization@freebsd.org Subject: Re: The status of docker Message-ID: <01255294-b0d6-3de9-6cde-671bd763a5a8@gjunka.com> In-Reply-To: <11fa9f16-0745-c86e-4820-fd9349b4d1ef@nomadlogic.org> 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> <11fa9f16-0745-c86e-4820-fd9349b4d1ef@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/02/2019 19:49, Pete Wright wrote: > > > 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. > Looks like that that's no longer true and hasn't been true for the past 2 years: https://containerjournal.com/2016/08/15/docker-not-just-linux-anymore/ But it also looks like something similar could have been achieved by replacing xhyve/Hyper-V with bhyve. If docker is open source then that shouldn't be a problem?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01255294-b0d6-3de9-6cde-671bd763a5a8>