apt2ostree VS eget

Compare apt2ostree vs eget and see what are their differences.


Build ostree images based on Debian/Ubuntu (by stb-tester)


Easily install prebuilt binaries from GitHub. (by zyedidia)
Our great sponsors
  • InfluxDB - Access the most powerful time series database as a service
  • Sonar - Write Clean Python Code. Always.
  • SaaSHub - Software Alternatives and Reviews
apt2ostree eget
6 11
71 496
- -
3.7 8.6
4 months ago about 1 month ago
Python Go
- MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of apt2ostree. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-01-11.
  • Why Use Make
    10 projects | news.ycombinator.com | 11 Jan 2023
    Hm yes now I remember that point about how the data is anonymous Python objects that you can pass around to functions.

    Are there any open source examples? I looked around the github account, but I mostly remember this tool


    I'd be interested in seeing the Python config and Ninja output, to see how it works. Right now it looks to me like the dependencies are more implicit than explicit, e.g. with your copen example


    The system I ended up with is more like Bazel, but it's not building containers, so it's a slightly different problem. But I'm interested in building containers incrementally without 'docker build'.

    I like the apt lockfile idea definitely ... However I also have a bunch of other blobs and tarballs, that I might not want to check into git. I guess you just put those in OSTree?

    Our config looks like this


    And all the code is in build/ninja* of the same repo

  • An ode to Flatpak (and Fedora Silverblue)
    6 projects | reddit.com/r/linux | 21 Aug 2022
    However, you can get pretty close yourself with a tool like this https://github.com/stb-tester/apt2ostree
  • Docker containers usually still reachable even if bound to
    5 projects | news.ycombinator.com | 22 Jun 2022
    With apt2ostree[1] we use lockfiles to allow us to version control the exact versions that were used to build a container. This makes updating the versions explicit and controlled, and building the containers functionally reproducible - albeit not byte-for-byte reproducible.

    [1]: https://github.com/stb-tester/apt2ostree#lockfiles

  • Reproducible builds for Debian: a big step forward
    4 projects | news.ycombinator.com | 12 Oct 2021
    On the subject of reproducible debian-based environments I wrote apt2ostree[1]. It applies the cargo/npm lockfile idea to debian rootfs images. From a list of packages we perform dependency resolution and generate a "lockfile" that contains the complete list of all packages, their versions and their SHAs. You can commit this lockfile to git.

    You can then install Debian or Ubuntu into a chroot just based on this lockfile and end up with a functionally reproducible result. It won't be completely byte identical as your SSH keys, machine-id, etc. will be different between installations, but you'll always end up with the same packages and package versions installed for a given lockfile.

    This has saved us on a few occasions where an apt upgrade had broken the workflow of some of our customers. We could see exactly which package versions changed in git history and roll-back the problematic package before working on fixing it properly. This is vastly better than the traditional `RUN apt-get install -y blah blah` you see in `Dockerfile`s.

    IMO it's also more convenient than debootstrap as you don't need to worry about gpg keys, etc. when building the image. Dependency resolution and gpg key stuff is done at lockfile generation time, so the installation process can be much simpler. In theory it could be made such that only dpkg is required to do the install, rather than the whole of apt, but that's by-the-by.

    apt2ostree itself is probably not interesting to most people as it depends on ostree and ninja but I think the lockfile concept as applied to debian repos could be of much broader interest.

    [1]: https://github.com/stb-tester/apt2ostree#lockfiles

    [2]: https://ostreedev.github.io/ostree/


Posts with mentions or reviews of eget. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-03-27.

What are some alternatives?

When comparing apt2ostree and eget you can also consider the following projects:

ostree - Operating system and container binary deployment and upgrades

fetch - Download files, folders, and release assets from a specific git commit, branch, or tag of public and private GitHub repos.

tflint - A Pluggable Terraform Linter

chromium - The official GitHub mirror of the Chromium source

pastel - A command-line tool to generate, analyze, convert and manipulate colors

bin - Effortless binary manager

micro-editor - A modern and intuitive terminal-based text editor

stew - 🥘 An independent package manager for compiled binaries.

flatpak-external-data-checker - A tool for checking if the external data used in Flatpak manifests is still up to date

proton-ge-custom - Compatibility tool for Steam Play based on Wine and additional components

nixpkgs - Nix Packages collection

flathub - Pull requests for new applications to be added