История изменений

Не докер, но контейнер

Кстати, интересно, а какие, собственно, известные разработчики софта сейчас пихают сборки в виде докер-контейнеров с упакованными в них зависимостями?

https://static.googleusercontent.com/media/research.google.com/en//pubs/archi...

Borg programs are statically linked to reduce
dependencies on their runtime environment

https://static.googleusercontent.com/media/research.google.com/en//pubs/archi...

There are many ways to achieve these hermetic images.
In Borg, program binaries are statically linked at build time to known-good library versions hosted in the company-wide repository. Even so, the Borg container image is not quite as airtight as it could have been: applications share a so-called base image that is installed once on the machine rather than being packaged in each container. This base image contains utilities such as tar and the libc library, so upgrades to the base image can affect running applications and have occasionally been a significant source of trouble.

Тут немного преувеличили, потому что это же надо такой софт написать чтобы тебе все сломала новая версия утилиты (даже не библиотеки) tar

Не докер, но контейнер

Кстати, интересно, а какие, собственно, известные разработчики софта сейчас пихают сборки в виде докер-контейнеров с упакованными в них зависимостями?

https://static.googleusercontent.com/media/research.google.com/en//pubs/archi...

Borg programs are statically linked to reduce
dependencies on their runtime environment

https://static.googleusercontent.com/media/research.google.com/en//pubs/archi...

There are many ways to achieve these hermetic images.
In Borg, program binaries are statically linked at build time to known-good library versions hosted in the company-wide repository. Even so, the Borg container image is not quite as airtight as it could have been: applications share a so-called base image that is installed once on the machine rather than being packaged in each container. This base image contains utilities such as tar and the libc library, so upgrades to the base image can affect running applications and have occasionally been a significant source of trouble.

Тут немного преувеличили, потому что это же надо такой софт написать чтобы тебе все сломала новая версия утилиты (даже не библиотека) tar

Не докер, но контейнер

Кстати, интересно, а какие, собственно, известные разработчики софта сейчас пихают сборки в виде докер-контейнеров с упакованными в них зависимостями?

https://static.googleusercontent.com/media/research.google.com/en//pubs/archi...

Borg programs are statically linked to reduce
dependencies on their runtime environment

https://static.googleusercontent.com/media/research.google.com/en//pubs/archi...

There are many ways to achieve these hermetic images.
In Borg, program binaries are statically linked at build time to known-good library versions hosted in the company-wide repository. Even so, the Borg container image is not quite as airtight as it could have been: applications share a so-called base image that is installed once on the machine rather than being packaged in each container. This base image contains utilities such as tar and the libc library, so upgrades to the base image can affect running applications and have occasionally been a significant source of trouble.

Тут немного преувеличили, потому что это же надо такой софт написать чтобы тебе все сломал новая утилита (даже не библиотека) tar

Не докер, но контейнер

Кстати, интересно, а какие, собственно, известные разработчики софта сейчас пихают сборки в виде докер-контейнеров с упакованными в них зависимостями?

https://static.googleusercontent.com/media/research.google.com/en//pubs/archi...

Borg programs are statically linked to reduce

dependencies on their runtime environment

https://static.googleusercontent.com/media/research.google.com/en//pubs/archi...

There are many ways to achieve these hermetic images.

In Borg, program binaries are statically linked at build time to known-good library versions hosted in the company-wide repository. Even so, the Borg container image is not quite as airtight as it could have been: applications share a so-called base image that is installed once on the machine rather than being packaged in each container. This base image contains utilities such as tar and the libc library, so upgrades to the base image can affect running applications and have occasionally been a significant source of trouble.

Тут немного преувеличили, потому что это же надо такой софт написать чтобы тебе все сломал новая утилита (даже не библиотека) tar