Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

proposal: use eatmydata for faster installations #155

Open
devkral opened this issue Mar 18, 2022 · 2 comments
Open

proposal: use eatmydata for faster installations #155

devkral opened this issue Mar 18, 2022 · 2 comments

Comments

@devkral
Copy link

devkral commented Mar 18, 2022

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.

@devkral devkral changed the title feature: use eatmydata for faster installations proposal: use eatmydata for faster installations Mar 18, 2022
@tianon
Copy link
Contributor

tianon commented Mar 24, 2022

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. 😬 🙈

@devkral
Copy link
Author

devkral commented Mar 25, 2022

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:

  1. Internal bootstrapping usage for different docker image flavors. This saves time and current.
  2. 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)
  • much faster docker-builds on weaker PCs possible
  1. Can be also used for other heavy syncing software

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants