Date: Fri, 29 Jan 2016 11:19:31 +0000 From: Ryan Holt <ryan@ryanholt.net> To: Sergey Zakharchenko <doublef.mobile@gmail.com> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: RE: Docker on FreeBSD Message-ID: <BLUPR08MB11702A0A4459D1401BA7F549B4DB0@BLUPR08MB1170.namprd08.prod.outlook.com> In-Reply-To: <CADYCxoOEWhFYsaDj%2BEbe3Z-c0jDGZScq3Fmy3PQQ1==k_MJqFg@mail.gmail.com> References: <BLUPR08MB1170DC886B5C33DC4E35884AB4C30@BLUPR08MB1170.namprd08.prod.outlook.com>, <CADYCxoOEWhFYsaDj%2BEbe3Z-c0jDGZScq3Fmy3PQQ1==k_MJqFg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Sergey, Thanks for the response. I've since moved to Gentoo, ZFS for Linux, and Do= cker. Works really well. Sent from Outlook Mail<http://go.microsoft.com/fwlink/?LinkId=3D550987> for= Windows 10 phone From: Sergey Zakharchenko<mailto:doublef.mobile@gmail.com> Sent: Friday, January 29, 2016 1:51 AM To: Ryan Holt<mailto:ryan@ryanholt.net> Cc: freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freebs= d.org> Subject: Re: Docker on FreeBSD Hello Ryan, 2016-01-21 23:15 GMT+03:00 Ryan Holt <ryan@ryanholt.net>: > Finished building a FreeBSD Head system today with the intent of using Do= cker. My condolences. > Is there a workaround to getting DNS inside of a container aside from man= ually building each image? The basic reason is no volume support in FreeBSD Docker port. The workaround is one of: - hacking the Docker port yourself, https://github.com/kvasdopil/docker/ is *a bit* incomplete and stale; - building a custom complicated and evil system around Docker that works around its design deficiencies and FreeBSD port incompleteness; - using Docker for building images only, and running them using vanilla jails + a custom complicated and evil system; - using jetpack instead and exposing yourself to a whole different set of problems ;) It's doable, but it is not for the faint of heart. I could share some improvements for the Docker port but kvasdopil@ seems too reluctant to make even the simplest changes (e.g. working around https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204897 :) ), #freebsd-docker is also rather apathetic and there's no way I'm going to hack on Go (yuck) alone and then just give it away (I'm in the 'custom complicated and evil system' camp). Best regards, -- DoubleF
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BLUPR08MB11702A0A4459D1401BA7F549B4DB0>