Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Mar 2020 08:44:13 -0500
From:      Valeri Galtsev <galtsev@kicp.uchicago.edu>
To:        freebsd-questions@freebsd.org
Subject:   Re: Technological advantages over Linux
Message-ID:  <042f3a16-110e-b1b5-feb3-73a2a3180882@kicp.uchicago.edu>
In-Reply-To: <20200316092527.882e58821f92097835310ef1@sohara.org>
References:  <20200214121620.GA80657@admin.sibptus.ru> <CAEJNuHwRs=6kOK9uiFzEAqCgSgvUb8Xm5o2VWnK-ND_zseowdg@mail.gmail.com> <20200214141600.GA82559@admin.sibptus.ru> <20200214204838.360c8f624397c659946bd764@sohara.org> <20200215063818.GE1482@admin.sibptus.ru> <20200215083359.367d8a3e9ddb4942df67d5b5@sohara.org> <20200316071102.GD90309@admin.sibptus.ru> <20200316092527.882e58821f92097835310ef1@sohara.org>

next in thread | previous in thread | raw e-mail | index | archive | help


On 3/16/20 4:25 AM, Steve O'Hara-Smith wrote:
> On Mon, 16 Mar 2020 14:11:02 +0700
> Victor Sudakov <vas@sibptus.ru> wrote:
> 
>> Steve O'Hara-Smith wrote:
>>> On Sat, 15 Feb 2020 13:38:18 +0700
>>> 	There are several iocage, ezjail, cbsd, bsdploy, jest to mention
>>> just a few. I find iocage suits my needs well enough.
>>
>> Oh, I've met an iocage person.
> 
> 	Well sort of, I use iocage to manage a bunch of jails on my NAS box
> but each one is a custom built server suiting my needs. I've never found a
> use for community built images, they never seem to suit my needs.

+1

I too only use what I built custom and configured to my "standards". The 
only "prebuilt" product I use is pfSense. The last to the contrary to 
community built [docker] images has rather large userbase.

Those community built images are loved by young researchers I work for. 
They need something fast, don't care to figure dependencies and don't 
want to put much effort into building what they need. Often they do not 
have the ability or time or both. So they are happy if the find what 
they need built by someone into docker image, they do not care how many 
people actually used that, if it is being updated (maintained) or just 
put together once and forgotten, etc.

When I am asked to make a docker image, I immediately see huge recurring 
burden, namely constant maintenance, and update of that. Pretty much as 
I keep up-to-date machines, and jails... Now, what ensures that that 
effort is used, namely that people who grabbed and started using that 
docker image will often come back and grab updated docker image? I'd 
like to ask Docker people: is there a "culture" of keeping up with 
updates between docker images end users? Psychologically I can't imagine 
that there is one, but I may be wrong.

Just my $0.02.

Valeri

> 
>> Steve, can iocage export thin provisioned images? If you publish an
>> iocage image e.g. of a Moodle server, will it contain the whole
>> underlying FreeBSD system within?
> 
> 	iocage export produces an image with everything. There are iocage
> plugins which are probably what you're looking for (but I've never used
> them).
> 
> 	https://iocage.readthedocs.io/en/latest/plugins.html
> 
> 

-- 
++++++++++++++++++++++++++++++++++++++++
Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247
++++++++++++++++++++++++++++++++++++++++



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?042f3a16-110e-b1b5-feb3-73a2a3180882>