From nobody Wed Apr 12 20:01:28 2023 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PxYhf34sBz44fpr for ; Wed, 12 Apr 2023 20:09:38 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-pj1-x1029.google.com (mail-pj1-x1029.google.com [IPv6:2607:f8b0:4864:20::1029]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PxYhd5KGZz3JqV for ; Wed, 12 Apr 2023 20:09:37 +0000 (UTC) (envelope-from jerry@seibercom.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=seibercom.net header.s=google header.b=dGGBtu2I; spf=pass (mx1.freebsd.org: domain of jerry@seibercom.net designates 2607:f8b0:4864:20::1029 as permitted sender) smtp.mailfrom=jerry@seibercom.net; dmarc=none Received: by mail-pj1-x1029.google.com with SMTP id 98e67ed59e1d1-2469f709ecaso410365a91.0 for ; Wed, 12 Apr 2023 13:09:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=seibercom.net; s=google; t=1681330175; x=1683922175; h=content-transfer-encoding:mime-version:organization:reply-to :references:in-reply-to:message-id:subject:to:from:date:from:to:cc :subject:date:message-id:reply-to; bh=OC37oRHYKoDK03k9f8fdVbi6Ch6eJq+WQfnRABvGMEI=; b=dGGBtu2I8Oq7K5q4fFCKSLIoto4olW//5O9t2uQq4Us+61IpintPoz/uboWJMvl7YF dHs+FXulPheklcaVyPjR5GqgbXoDyNtR4spUmmkwDHu/4gTEUcMASNlOZSBfdT67pRpX 47lLMcOnvZ69Tg3wUi6dU5M0Vg9OqDXpTUsZA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681330175; x=1683922175; h=content-transfer-encoding:mime-version:organization:reply-to :references:in-reply-to:message-id:subject:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=OC37oRHYKoDK03k9f8fdVbi6Ch6eJq+WQfnRABvGMEI=; b=YnWm5inNOF8iM7mxpy4XmQa+BrgOweCb0qCv7HQiapRBrnrckzHexoAKZGSNsH0PE/ tiTTLzuwlUJKXsFMlnA+sTmTyadQ5AWupk58EpXmFh+S/W7UBW2VU8ISaLS5gzPR304D LIdQhh0WDM3T7GUUfjHKo64agP9/1Srt/zkQTzDjYVsTjU4aSEmNZQsem949ZtQP8g8s ka4flZO93x2PJmsam996OOnpYwzbAzeAESOoaBfjxyTsoTP9WNyOkAdP1A3LN7SDC3sU EbVaHv3Qb5ZcAIGtXpyoDEveZDnq+6QhEq7pVZVn5G0xnZaRIwY9l2MUDZ2g7oYkCkzF UEaw== X-Gm-Message-State: AAQBX9ehrUEJ8aM55qUHUECSLoHNL9JaHypgPjJtL+4Zvl+IVqo6Ub4i ku5XC5QFofwFs1wgTnsnEyY9htEWHzjHtxFvHok= X-Google-Smtp-Source: AKy350Yy/hSwpz8LzgGljWZvi1m78FauRq25YX7FrfkmWwUlnWUKbhOqbjFzKx4/h/JBaQmWVNEBAg== X-Received: by 2002:a81:e83:0:b0:54f:7970:2192 with SMTP id 125-20020a810e83000000b0054f79702192mr3245397ywo.2.1681329690892; Wed, 12 Apr 2023 13:01:30 -0700 (PDT) Received: from mystic.seibercom.net (cpe-71-77-18-211.nc.res.rr.com. [71.77.18.211]) by smtp.gmail.com with ESMTPSA id ck8-20020a05690c0b8800b0054f56baf3f2sm1712694ywb.122.2023.04.12.13.01.29 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 12 Apr 2023 13:01:29 -0700 (PDT) Received: from localhost (scorpio.seibercom.net [192.168.1.102]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: jerry@seibercom.net) by mystic.seibercom.net (Postfix) with ESMTPSA id 4PxYWD61cTz26Hl for ; Wed, 12 Apr 2023 16:01:28 -0400 (EDT) Date: Wed, 12 Apr 2023 16:01:28 -0400 From: "Gerard E. Seibert" To: "User Questions" Subject: Re: Docker Message-ID: <20230412160128.00005bd4@seibercom.net> In-Reply-To: References: <20230329053443.6ADA6B6AFED5@dhcp-8e64.meeting.ietf.org> <8E16D624-2655-4A10-844A-93E4F63E9859@gromit.dlib.vt.edu> <078a1cf8-7ae2-c593-615b-f5f37fa2b3eb@timpreston.net> <06be3a1e-9319-1a21-88b9-4f87328ee127@timpreston.net> <34b4b76e-1c41-4cfb-9e86-856f01e8abc9@app.fastmail.com> <6002f636-310b-a9fd-b82f-346618976983@timpreston.net> Reply-To: "User Questions" Organization: seibercom NET X-Mailer: Claws Mail 4.1.0 (GTK 3.24.33; x86_64-w64-mingw32) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [1.50 / 15.00]; REPLYTO_EQ_TO_ADDR(5.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[seibercom.net:s=google]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; HAS_REPLYTO(0.00)[questions@freebsd.org]; DMARC_NA(0.00)[seibercom.net]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::1029:from]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_THREE(0.00)[4]; HAS_ORG_HEADER(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; TO_DN_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[seibercom.net:+]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; GREYLIST(0.00)[pass,body] X-Rspamd-Queue-Id: 4PxYhd5KGZz3JqV X-Spamd-Bar: + X-ThisMailContainsUnwantedMimeParts: N On Wed, 12 Apr 2023 15:38:47 +0200, Mario Marietto stated: > ---> Docker will NEVER run on FreeBSD, because Docker is built on > technologies which only exist in the Linux kernel. I have read several articles that state Docker can run on MS Windows. If that is true, and I have not seen anything that disproves it, then it can run on technologies other than those found in the Linux kernel. =20 > I don't agree with this. In my humble opinion Docker can run on > FreeBSD. For sure,not using the same technology that it uses on > Linux. FreeBSD does not use the kernel of Linux,so it cannot lean on > it,but I'm sure that it can lean on a lot of linux features that have > already been implemented on FreeBSD. Maybe they should be improved. > And on some other technologies that can be created almost from > scratch. In my opinion Docker does not work in FreeBSD not for > technical reasons. I'm sure that the technical problems can be solved > if there is the will,the need to overcome them. Honestly I think it > doesn't happen because there are habits and internal beliefs in every > group of OS developers. I'm talking about a certain type of > closed-mindedness and sense of belonging in a group that you don't > want to be scratched by tools that come from other types of OS > cultures. Docker is not needed in FreeBSD because there are already > similar tools that are working well and many systems engineers have > spent time and money to learn how to administer them. If docker were > implemented, these system administrators would continue to use their > favorite tools (jails), even in the industry / market there are just > as many well done. Probably a very few FreeBSD admins even want an > influx of users from linux who could switch to freebsd because of > that tool that wasn't there before but "now" it is there. >=20 > On Wed, Apr 12, 2023 at 4:29=E2=80=AFAM Tim Preston > wrote: >=20 > > Hi Mario, > > > > I may not have been clear enough in my last email. > > > > Docker will NEVER run on FreeBSD, because Docker is built on > > technologies which only exist in the Linux kernel. > > > > FreeBSD cannot run Linux containers, it can only run FreeBSD jails. > > > > It's not because FreeBSD programmers think they're more special > > than Linux programmers, it's just not technically possible. > > > > If you want to run any of the Docker images available on the > > internet you can try the tooling linked by Dave, which MIGHT let > > you run SOME Docker images inside a FreeBSD jail, using FreeBSD's > > Linux compatibility layer. But these images really require a Linux > > kernel to run properly. > > > > A better approach, if the applications you want to run are > > available in ports, or if the source code builds on FreeBSD, is to > > run them natively in a jail using tools similar to Docker like > > Bastille ( https://bastillebsd.org/) or Pot > > (https://github.com/bsdpot/pot). > > > > I hope some of this helps. > > > > Tim > > > > > > On Tue, 11 Apr 2023, at 8:45 PM, Mario Marietto wrote: > > > > ---> If you want the full Linux-compatible Docker experience, then, > > yes,use Linux, either in a VM, or directly. I don't think there are > > many FreeBSD people who use only 1 OS, we are by and large > > pragmatic people. It's ok to use different tools in different > > situations. > > > > But home users usually are poor people. To have a good computer > > means often to be lucky. I mainly use FreeBSD because I feel good > > when I use many of its tools. But it often happens that I also need > > to be able to have some different tool that I like because I tried > > it in a different system and I liked it. Docker is one of those > > tools. Users love it,even today,but it is becoming old. For sure > > there are good technical reasons behind this "love". The > > development of Docker on FreeBSD stopped a lot of years ago. And > > the reasons for that stop is not only caused by technical > > reasons,in my opinion,but,as I said,even by a form of > > discrimination. The storic FreeBSD users have been trained using > > its own tools and they won't change. They don't want to spend money > > to develop a new/old tool that will enrich the tools park ? This > > mindset is not focused on the satisfaction of those users that > > could migrate or that want to try FreeBSD,after having used another > > OS. It is some kind of sectarian mentality. Yes I can run a VM > > running Linux,but this will waste resources on the machine. Why > > should I run a whole VM if I need only to run a tool ? If the tool > > is not widely used,ok,developing it is not worth it. But we are > > talking of widely used tools here and Docker is one of those tools. > > > > On Tue, Apr 11, 2023 at 12:26=E2=80=AFPM Mario Marietto > > wrote: > > > > For sure there are users / developers that are in the middle,like it > > happens in the political area. I like this kind of person. I'm one > > of those people. My criticism is against those users and developers > > that show an exaggerated "love" and fidelity towards a system, > > whether by ideology, whether by habit, or by commercial reasons. > > I'm a frequent visitor to various freebsd forums and I often read > > opinions radicalized on linux technologies that should not enter > > the freebsd world, simply because in Freebsd there are already > > excellent tools that do their job well. Yes,they work well,but why > > not add more and different tools that which would allow the > > creation of bridges between different operating systems ? > > > > On Tue, Apr 11, 2023 at 12:17=E2=80=AFPM Dave Cottlehuber > > wrote: > > > > On Tue, 11 Apr 2023, at 09:44, Mario Marietto wrote: > > > Tim,you are wasting your time. It seems that all of these (good) > > > FreeBSD developers don't want you to use Linux technologies if > > > you have chosen FreeBSD as the main OS. That's not good and it > > > sounds like a discriminatory attitude. > > > > I think you're mis-representing the position of a lot of people > > here; please don't do that. > > > > The fast-moving Docker.com tech has been moving towards a > > standards-based "Open Container" https://opencontainers.org/ > > definition, and many people have worked across the standard, the > > implementation, kernel, & tooling, now in ports on FreeBSD, to make > > this possible. Just a few examples: > > > > - https://github.com/samuelkarp/runj/ > > - https://github.com/dfr/ocijail/ > > - https://medium.com/@dfr/oci-containers-for-freebsd-512a6df2bc85 > > > > It would be great to get your feedback on one of these and see what > > you tried, and where it breaks with your expectations. > > > > While it may be possible to run many linux containers with this > > tooling, systemd and other linux-specific things could be present > > in any container you pull, from systemd, to filesystem > > requirements, and expecting all of these to work seamlessly is > > unrealistic. > > > > If you want the full Linux-compatible Docker experience, then, yes, > > use Linux, either in a VM, or directly. I don't think there are many > > FreeBSD people who use only 1 OS, we are by and large pragmatic > > people. It's ok to use different tools in different situations. > > > > A+ > > Dave > > > > > > > > -- > > Mario. > > > > > > > > -- > > Mario. > > > > > > >=20