Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105675
MIME-Version: 1.0
References: <CA+4wLCA3qR9qK065OwYzuaxWeFhK8g_GWa3gp9hhk6Nzy81=7g@mail.gmail.com>
 <CAAfnsFUM2HenDT1mBAnVVEFOPDoQB5JcyhU3DO2JczgKR41eng@mail.gmail.com> <CAEZPtU5kx7N4zBBCvnzRyyc1r=R-xOpfn7HyXUptSzj7nokS9g@mail.gmail.com>
In-Reply-To: <CAEZPtU5kx7N4zBBCvnzRyyc1r=R-xOpfn7HyXUptSzj7nokS9g@mail.gmail.com>
Date: Sat, 11 May 2019 12:49:46 +0200
Message-ID: <CAAfnsFUut6d3jTv=-Fz1chARSoPYYMtv4fi3YVY1LuUdzd97FA@mail.gmail.com>
To: Pierre Joye <pierre.php@gmail.com>
Cc: Martins Sipenko <martins.sipenko@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] PHP Docker images
From: peterkokot@gmail.com (Peter Kokot)

On Sat, 11 May 2019 at 06:12, Pierre Joye <pierre.php@gmail.com> wrote:
>
> On Fri, May 10, 2019, 2:06 PM Peter Kokot <peterkokot@gmail.com> wrote:
>
> >
> > The images for such C software are one of the more useless ones. Snaps
> > or custom Linux repositories are the way to go here. Because of the
> > installation time. Building several extensions from source is really
> > time consuming...
>
>
> Maybe this is exactly why docker images are nice. You do not build them but
> once (on dockerhub f.e.) and users only grab them. Just maybe...
>
> best
> Pierre

Yes, theoretically :) There are actually more cases where you will
build them more than once. Almost several times per day. For example,
to build intl extension one must do:
docker-php-ext-install intl and also install dependencies that belong
to it. Imagine now doing this for a normal PHP environment which is
about several more extensions, some pecl ones and you get to an
installation time of almost 10 minutes (over the thumb). Docker
registries are not that common as we think. And with building the same
Docker image using Linux repositories the installation becomes a
matter of seconds (without worrying which extensions need another apk
add --no-cache libfoo or apt install libfoo-dev) and then also
cleaning those dev packages after the build.

-- 
Peter Kokot