You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a very interesting idea -- I think it would make a lot of sense for most Docker images to have APT use eatmydata, but unfortunately I don't think it's entirely a reasonable default for every use of the Docker images. 😬 🙈
Luckily this is no problem because eatmydata has two modes of operation:
one which replaces the default call of apt/apt-get via symlink (the real program can be still used without using eatmydata by accessing it via the full path)
and one where you have to specify it manually (default): eatmydata apt ....
This means we can have an opt-out/opt-in mechanism.
It would be enough to preinstall it (opt-in).
With eatmydata preinstalled (and documented) there are multiple advantages:
Internal bootstrapping usage for different docker image flavors. This saves time and current.
derivated images could use it out of the box.
less space usage (no need to install it in the first step, often a build layer)
what
apt uses syncs a lot. This slows down the installation of packages.
The main advantage safer updates are not relevant for docker as everything is thrown away whenever an error occurs.
Proposal
use eatmydata in images. This speeds up the installation/updates of packages dramatically.
The text was updated successfully, but these errors were encountered: