Page 1 of 1

To avoid the end user having to download

Posted: Tue Feb 11, 2025 6:36 am
by sujonkumar6300
All the dependencies used by each developer, and to ensure that each package will work independently of the others installed on the system, the de facto choice has been to convert dynamic libraries into statically linked objects. Of course, this means that when a shared library is updated, each of the applications that use it must also be updated. But in an era of permanent Internet connection, this idea has been favored by the market.

Distribution and virtual servers

Putting the two themes together, Docker's main contribution is that it bahamas phone number data turns the cumbersome deployment of virtual servers into a simple deployment of applications — And, of course, of applications packaged in a fashionable way, with the minimum of dependencies.

From a purely DevOps perspective, this sounds great. However, it also involves great risks, as illustrated by the texts written on the subject by two of the Debian GNU/Linux developers, Joey Hess [1] and Erich Schubert [2], among others.

First of all, irresponsible use of Docker (even if it is recommended by its developers) can lead us to trust software whose origin is not necessarily what we expect, without knowing what the changes consist of and how they will affect us. Packages that claim to be official for certain distributions have been shown to have been altered, which should make any system administrator think badly.