Date: Wed, 12 Apr 2023 15:52:52 +0100 From: Steve O'Hara-Smith <steve@sohara.org> To: Paul Pathiakis <pathiaki2@yahoo.com> Cc: Mario Marietto <marietto2008@gmail.com>, Tim Preston <tim@timpreston.net>, freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: Docker Message-ID: <20230412155252.5e38ea4728bd52dc798852fc@sohara.org> In-Reply-To: <1535315680.2770963.1681309684072@mail.yahoo.com> References: <20230329053443.6ADA6B6AFED5@dhcp-8e64.meeting.ietf.org> <8E16D624-2655-4A10-844A-93E4F63E9859@gromit.dlib.vt.edu> <078a1cf8-7ae2-c593-615b-f5f37fa2b3eb@timpreston.net> <CA%2B1FSij9j922Nvv1Vhn43HznwpyGT99UZsU674G9hHWzR=UhvQ@mail.gmail.com> <06be3a1e-9319-1a21-88b9-4f87328ee127@timpreston.net> <CA%2B1FSijc%2B-OLNsyFNdR=jP3VzMi4zUE92i5iv9Pfg6AryDy_KQ@mail.gmail.com> <34b4b76e-1c41-4cfb-9e86-856f01e8abc9@app.fastmail.com> <CA%2B1FSihVrJ8cZ4ZU6mMr0sKJsZ98V4fh2vpDLugw7MGj-%2BEBPg@mail.gmail.com> <CA%2B1FSijL50mQ-HveBA4HZeNkSoaORv=aty-15nNLzn9amzY_nw@mail.gmail.com> <6002f636-310b-a9fd-b82f-346618976983@timpreston.net> <CA%2B1FSigV_pPwVW%2BDd8WZYGcNQVt7%2BYOcsnJFoRhS6jL5A636pg@mail.gmail.com> <20230412150350.12f97eb2c9dd566b8c8702d2@sohara.org> <CA%2B1FSihVPCQ6tp8u=aqnLyyOPpCMrnhYGcC8bCUgRbFHTdY5sA@mail.gmail.com> <1535315680.2770963.1681309684072@mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20230412155252.5e38ea4728bd52dc798852fc>