Re: Docker

A lot of years ago I found this interesting project :
http://www.colinux.org/

I've been always fascinated by it :

*Cooperative Linux* is the first working *free* and *open source* method
for optimally running Linux on Microsoft Windows natively. More
generally, *Cooperative
Linux* (short-named coLinux) is a port of the Linux kernel
<http://www.kernel.org> that allows it to run cooperatively alongside
another operating system on a single machine. For instance, it allows one
to *freely* run Linux on Windows 2000/XP/Vista/7, *without* using a
commercial PC virtualization software such as VMware <http://www.vmware.com>,
in a way which is much more optimal than using any general purpose PC
virtualization software.

How could it be hard to create something like this ? I mean,a cooperative
kernel between the linux kernel and the freebsd kernel. A sort of Linux
kernel that will run alongside the FreeBSD processes. Maybe even integrated
within the (centos) linux emulation layer that already exists under
FreeBSD. In the end,what's missing on the LEL is a kernel.



On Wed, Apr 12, 2023 at 4:53 PM Steve O'Hara-Smith <steve@sohara.org> wrote:

> On Wed, 12 Apr 2023 14:28:04 +0000 (UTC)
> Paul Pathiakis <pathiaki2@yahoo.com> wrote:
>
> >  I believe the simplest thing would be to wrap jails or iocage in an
> > interface that looks like and behaves Docker-like. Many people these days
> > don't care what's under the hood.  All they care about is familiarity of
> > interface (GUI)
>
>         Docker is many things - the UI the least important.
>
>         Docker is a mechanism for creating container images from text
> descriptions in Dockerfiles each of which defines an overlay to be applied
> to a base image (either an OS image or one defined in a Dockerfile).
>
>         A common use for this mechanism is to assemble servers by picking
> an
> off-the-shelf image with the right service(s) and building a custom
> configuration/application layer on top of it. Rinse, repeat until every
> element of a stack is defined and get swarm or kubernetes to deploy and
> manage it. This use depends strongly on the rich public library of
> application layers. In order to have this in FreeBSD we'd either have to be
> able to use the Linux images directly or we'd need a similar library of
> FreeBSD images (OCI compliant if we want kubernetes) - which is an awful
> lot
> of playing catch up.
>
>         Another use for this mechanism is to assemble complex application
> stacks (such as development environments) so that they can be used easily.
> Many do this sort of thing with iocage, nomad, or base system jails and
> ansible or puppet or ... Docker is almost certainly more convenient than
> any
> of these.
>
> --
> Steve O'Hara-Smith
> Odds and Ends at http://www.sohara.org/
>


-- 
Mario.