[kwlug-disc] Docker on VPSes

[Benjamin Tompkins]

To add to this, my understanding of containers of any type is that they are
best used for ephemeral work loads.

So for instance if you have a large web front end each session that
connects gets it's own container that is created on demand.  The client
does their thing and the contain then gets destroyed and goes away.  Any
and all data is loaded/saved through the container to a backing object
store/database/however the site is designed.  This helps to greatly limit
the footprint of the application.  To my understanding this is how the
Gmail interface is run.

For this case, you would likely break it into to two parts.  First is the
container that would have the Apache/nginx frontend with Drupal that would
then connect back to a database that is on (potentially) the host.  Second,
you would need some sort of load balancer/proxy that would make the call
back to the container orchestration to instantiate the container for the
client to connect to.

So now the question becomes, do you want to manage all of that?

On Tue, Jan 22, 2019 at 9:46 AM Khalid Baheyeldin <kb at 2bits.com> wrote:

> Unless you want to learn Docker, there is not need to use it (in this
> case).
>
> Both Drupal 7 and Drupal 8 run fine on Ubuntu 18.04 and the supplied
> version of PHP on it (7.2). So the two sites can co-exist, each in its own
> webroot directory, and each on a separate database.
>
> Lots of effort has been put to make sure that even D7 works.
>
> https://www.drupal.org/project/drupal/issues/2947772
>
> The only thing to check is contrib modules. The main ones that are commonly
> used work fine, but there may be some outliers.
>
> I switched my Linode VPS to 7.2 using PPA's by the Debian PHP maintainer,
> and everything works. The next step is to upgrade that VPS to 18.04, but
> there is no urgency because I already have PHP 7.2 on it.
>
> On Tue, Jan 22, 2019 at 4:15 AM Paul Nijjar via kwlug-disc <
> kwlug-disc at kwlug.org> wrote:
>
>> I asked a version of this question during the last Drupal meeting, so
>> apologise for the rerun.
>>
>> I am working on migrating a LAMP application -- Drupal, as it turns
>> out -- from a VPS on Linode onto a different VPS on Linode. (Yes, I
>> really want to migrate to a new instance and not just upgrade the
>> existing one.)
>>
>> It seems that Docker is the cool new thing to use for deploying
>> applications. It sounds as if Docker is good for scaling things out,
>> and for allowing different versions of LAMP components (different
>> versions of PHP, for example) to exist on the same VPS when they are
>> used by different applications. But does it make sense if you are
>> sticking with a standard LAMP configuration on a standard Ubuntu
>> install? It might be possible to containerize this application, but
>> would it be worth the trouble? What advantages would there be?
>>
>> I am also confused how one keeps all of these containerized images up
>> to date, and even why I should trust images that come from
>> hub.docker.com . I trust Ubuntu/Debian updates because I understand
>> the social infrastructure that makes them relatively trustworthy. I
>> also understand that I can upgrade these components with an "apt
>> upgrade". I do not know how people do this in the Docker world.
>>
>> Help? There are a bunch of tutorials in getting started with Docker,
>> but not much about when to choose it, and under what situations it
>> does/does not make sense.
>>
>> - Paul
>>
>>
>> --
>> http://pnijjar.freeshell.org
>>
>> _______________________________________________
>> kwlug-disc mailing list
>> kwlug-disc at kwlug.org
>> http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org
>>
>
>
> --
> Khalid M. Baheyeldin
> 2bits.com, Inc.
> Fast Reliable Drupal
> Drupal optimization, development, customization and consulting.
> Simplicity is prerequisite for reliability. -- Edsger W.Dijkstra
> Simplicity is the ultimate sophistication. -- anonymous
>
> _______________________________________________
> kwlug-disc mailing list
> kwlug-disc at kwlug.org
> http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://kwlug.org/pipermail/kwlug-disc_kwlug.org/attachments/20190122/41097161/attachment.htm>