Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 29 Jan 2016 02:45:24 -0500 (EST)
From:      Matthew Veety <mveety@gmail.com>
To:        freebsd-virtualization@freebsd.org
Subject:   Re: Docker on FreeBSD
Message-ID:  <alpine.BSF.2.20.1601290243060.28161@localhost>
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

On Fri, 29 Jan 2016, Sergey Zakharchenko wrote:

> 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 Docker.
>
> My condolences.
>
>> Is there a workaround to getting DNS inside of a container aside from manually 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=204897 :) ),
> #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

What needs to be done with docker to get it running better on FreeBSD? Is 
there any place with a list of bugs or a todo list? I would be interested 
in getting it working better.

--
Veety




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1601290243060.28161>