Date: Wed, 12 Apr 2023 16:52:14 +0200 From: Mario Marietto <marietto2008@gmail.com> To: "Steve O'Hara-Smith" <steve@sohara.org> Cc: Tim Preston <tim@timpreston.net>, freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: Docker Message-ID: <CA%2B1FSiha57PsNc1FoAWWCU8PNmhSbzX3Gd-j6ti7Ris_FSv-DA@mail.gmail.com> In-Reply-To: <20230412153039.bb0598c1f8b050ea8d4f40b9@sohara.org> 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> <20230412153039.bb0598c1f8b050ea8d4f40b9@sohara.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--00000000000011859805f924c30b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable ----> I believe the simplest thing would be to wrap jails or iocage in an interface that looks like and behaves Docker-like. Come on man. It's not only a matter of graphical interface. A lot of users may want to use docker on another OS because they already have learnt how to use it,so the commands used in Linux should be the same when it is ported on another OS like FreeBSD. And since there are a lot of images on the internet,they also want to reuse them. So the ported docker should be able to reuse those images ---> Many people these days don't care what's under the hood. All they care about is familiarity of interface (GUI) could be true for the newbies (not very experienced users). Anyway,if you want to "copy" only the graphical part the project will die because as I said the ported docker should work as close as possible to the original one. We can't forget how hard it is to change habits. ---> There's a *lot* of work to be done to achieve this mostly in the Linux emulation layer. I can imagine. So,maybe this is not the way to go. ---> Is there enough interest to create a critical mass of images ? maybe. If it's easier and intuitive. If there are a lot of docker images already created it means that Docker reached the goal to become a tool for the masses. On Wed, Apr 12, 2023 at 4:30=E2=80=AFPM Steve O'Hara-Smith <steve@sohara.or= g> wrote: > On Wed, 12 Apr 2023 16:13:05 +0200 > Mario Marietto <marietto2008@gmail.com> wrote: > > > I'm interested to know what you mean for "real needs", > > I mean real problems that are solved by having a FreeBSD > implementation of docker. IOW what would people use it for. > > For example one goal to be able to use the off-the-shelf images > available on docker.io (or other linux images) with docker and/or > kubernetes so as to be able to migrate application stacks to a FreeBSD > base. > There's a *lot* of work to be done to achieve this mostly in the Linux > emulation layer. I rather suspect that this is what most people expect of > docker and I can certainly see how it could be used in real world > applications and make FreeBSD an alternative to Linux as a host OS. > > Another goal is to be able to create layered FreeBSD based > container images from Dockerfiles and share (publicly or with a limited > group) them in the same way as Linux container layers are then that shoul= d > be rather less work - and ocijail seems to be a starting point. Is this > something people want to do ? Does Docker provide any benefits over > Nomad/iocage/cbsd for this use ? Is there enough interest to create a > critical mass of images ? > > -- > Steve O'Hara-Smith > Odds and Ends at http://www.sohara.org/ > --=20 Mario. --00000000000011859805f924c30b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr">----> I believe the simplest thing wou= ld be to wrap jails or iocage in an interface that looks like and behaves D= ocker-like.</div><div dir=3D"ltr"></div><div dir=3D"ltr"><br></div><div>Com= e on man. It's not only a matter of graphical interface. A lot of users= may want to use docker on another OS because they already have learnt how = to use it,so the commands used in Linux should be the same when it is porte= d on another OS like FreeBSD. And since there are a lot of images on the in= ternet,they also want to reuse them. So the ported docker should be able to= reuse those images</div><div><div dir=3D"ltr"><br></div><div dir=3D"ltr">-= --> Many people these days don't care what's under the hood.=C2= =A0 All they care about is familiarity of interface (GUI)</div></div><div><= br></div><div>could be true for the newbies (not very experienced users). A= nyway,if you want to "copy" only the graphical part the project w= ill die because as I said the ported docker should work as close as possibl= e to the original one. We can't forget how hard it is to change habits.= <br></div><div><br></div><div>=C2=A0---> There's a *lot* of work to= be done to achieve this mostly in the Linux emulation layer.</div><div><br= ></div><div>I can imagine. So,maybe this is not the way to go. <br></div><d= iv><br></div><div>---> Is there enough interest to create a critical mas= s of images ?</div><div><br></div><div>maybe. If it's easier and intuit= ive. If there are a lot of docker images already created it means that Dock= er reached the goal to become a tool for the masses. <br></div></div><br><d= iv class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Apr = 12, 2023 at 4:30=E2=80=AFPM Steve O'Hara-Smith <<a href=3D"mailto:st= eve@sohara.org">steve@sohara.org</a>> wrote:<br></div><blockquote class= =3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg= b(204,204,204);padding-left:1ex">On Wed, 12 Apr 2023 16:13:05 +0200<br> Mario Marietto <<a href=3D"mailto:marietto2008@gmail.com" target=3D"_bla= nk">marietto2008@gmail.com</a>> wrote:<br> <br> > I'm interested to know what you mean for "real needs",<b= r> <br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 I mean real problems that are solved by having = a FreeBSD<br> implementation of docker. IOW what would people use it for.<br> <br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 For example one goal to be able to use the off-= the-shelf images<br> available on <a href=3D"http://docker.io" rel=3D"noreferrer" target=3D"_bla= nk">docker.io</a> (or other linux images) with docker and/or<br> kubernetes so as to be able to migrate application stacks to a FreeBSD base= .<br> There's a *lot* of work to be done to achieve this mostly in the Linux<= br> emulation layer. I rather suspect that this is what most people expect of<b= r> docker and I can certainly see how it could be used in real world<br> applications and make FreeBSD an alternative to Linux as a host OS.<br> <br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 Another goal is to be able to create layered Fr= eeBSD based<br> container images from Dockerfiles and share (publicly or with a limited<br> group) them in the same way as Linux container layers are then that should<= br> be rather less work - and ocijail seems to be a starting point. Is this<br> something people want to do ? Does Docker provide any benefits over<br> Nomad/iocage/cbsd for this use ? Is there enough interest to create a<br> critical mass of images ?<br> <br> -- <br> Steve O'Hara-Smith<br> Odds and Ends at <a href=3D"http://www.sohara.org/" rel=3D"noreferrer" targ= et=3D"_blank">http://www.sohara.org/</a><br>; </blockquote></div><br clear=3D"all"><br><span class=3D"gmail_signature_pre= fix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature">Mario.<br></d= iv> --00000000000011859805f924c30b--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B1FSiha57PsNc1FoAWWCU8PNmhSbzX3Gd-j6ti7Ris_FSv-DA>