Date: Wed, 23 Jan 2019 21:08:59 +0000 From: Grzegorz Junka <list1@gjunka.com> To: ss griffon <ssgriffonuser@gmail.com>, "Patrick M. Hausen" <hausen@punkt.de> Cc: freebsd-virtualization@freebsd.org Subject: Re: The status of docker Message-ID: <5e0f5b46-3508-c29c-2e05-d3e97154512f@gjunka.com> In-Reply-To: <CAFYJ9eixff0NWKHhJWj=WBQ7TgQ26GODXtBDWxBXvuR62tPcuQ@mail.gmail.com> References: <089e330d-2761-2440-3b7f-dd22e9088af5@gjunka.com> <9A01020A-7CC6-4893-A425-11A7BF736F4E@ultra-secure.de> <42f59b63-fdc7-306f-d836-83533741a86c@FreeBSD.org> <CAG=rPVfTZnYc6%2BDjtk0SjkqijJQh6uA1G9VWEBsYy4aDYvYEgQ@mail.gmail.com> <CC0F6FB5-7939-4586-86DD-B5548E0043C3@punkt.de> <5c926314-adce-dba1-f5ce-2fda35e1aeba@gjunka.com> <FDDC8A58-8AD3-4D07-B0B3-0BDFA214ABA0@punkt.de> <1548c51e-49ba-4113-5ade-5515b77a3a44@gjunka.com> <4643A871-4AD6-4C25-AEA7-7BA85B873A19@punkt.de> <CAFYJ9eixff0NWKHhJWj=WBQ7TgQ26GODXtBDWxBXvuR62tPcuQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23/01/2019 03:21, ss griffon wrote: > I'm a bit late to the game, but I wanted to add my 2 cents. I don't > see the benefit of implementing "docker" in FreeBSD. If you are just > implementing the linux system calls i.e. using the linuxulator, then > you lose any benefits of running on FreeBSD. It seems like > implementing the docker interfaces, like a Dockerfile, registry > support and networking switches using FreeBSD specific implementations > would be extremely helpful. Especially for the CI/CD workflow. > > For example: > #Dockerfile > > #Pull a image from registry and create a new dataset with snapshot. > #Registry could be http, ftp or any other transfer protocol. > FROM FreeBSD:RELEASE-11.2 > > #Copy app directory into the jailed directory. Perhaps setting system > immutable flag. > COPY ./app /app > > #Use pf to route to port 80 from the host. Or use vnet > EXPOSE 80 > > #Run a command in the jail to prepare the new image. > RUN env ASSUME_ALWAYS_YES=yes pkg install bash nginx uwsgi py36-flask > > #Mark the startup command > CMD /bin/sh /etc/rc > > > The above would be very familiar to docker users and can be used to > generate a standards compliant image (I believe there was a project > jetpack that did something like this). Creating a OCI compliant image > would probably be the first step to using kubernetes, but I haven't > really spent any time looking at kubernetes. > > We could also add extensions for using resource limits, capsicum, > devd, security levels etc. The other cool thing is this could all be > run inside a jail using heirarchical jails. > Isn't implementing "docker" on FreeBSD the same as implementing OCI specification, i.e. runtime-spec? Seeing that OCI was founded by Docker I would have thought they align the docker implementation with the spec? Then to extend that question, wouldn't adding support for docker to FreeBSD mean to add OCI compliance layer to jails? I don't think the plan is to add support for Linux containers, or "containerization", to FreeBSD kernel? GrzegorzJ
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5e0f5b46-3508-c29c-2e05-d3e97154512f>