apt2ostree
silverblue-site
Our great sponsors
apt2ostree | silverblue-site | |
---|---|---|
6 | 39 | |
93 | 44 | |
- | - | |
0.0 | 3.8 | |
over 1 year ago | 11 months ago | |
Python | HTML | |
- | GNU General Public License v3.0 or later |
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.
apt2ostree
-
Why Use Make
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
https://github.com/stb-tester/apt2ostree
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
https://github.com/oilshell/oil/blob/master/core/NINJA_subgr...
And all the code is in build/ninja* of the same repo
-
An ode to Flatpak (and Fedora Silverblue)
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 127.0.0.1
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
-
Any plans for an immutable Debian desktop?
If you have time to test things, you can try to use ostree to manage a Debian installation. This is what Silverblue uses. Their is already a tool to create APT-based ostree images.
- Lockfiles for packages in a Debian/Ubuntu rootfs
-
Reproducible builds for Debian: a big step forward
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/
silverblue-site
-
Looking for a light distro with good privacy
Fedora; from its 'flagship' Workstation, to their glorious Spins and their Immutable Desktops
-
What are some of the more innovative linux distributions?
Fedora Silverblue - pretty well-known at this point, but it’s championing immutability
-
A discussion about the Ultimate Linux Desktop
Couldn't have said it better!
-
Been away from Linux for many years
An example of an installable immutable OS is Fedora Silverblue. Notably, you can change the "distro" flavor of Silverblue to try out KDE and then just flip back to Gnome. Each change is seen as an "update" that just moves you over to the new GUI. The article below explains a bit more.
-
I need something stable in my life...
I guess something like Fedora Silverblue might offer you something (to paraphrase) "stupid proof". For example, in this case the rpm-ostree rollback command would have been sufficient. Disclaimer: rpm-ostree builds images, therefore it's by necessity slower than apt. Futhermore, until this change is merged and deployed you'd have to reboot for the changes to apply. You might want to look into Distrobox as well, perhaps it can solve your problems without having to change your distro.
-
Nobara is letting me down lately.
However, I'll add one more that I'm especially fond of. It's one of the most 'stable'\1]) Linux desktop systems\2]) without sacrificing access to the latest kernel-updates and packages. It comes bundled with everything\3]) necessary for productivity right out of the box and is built on top of the fundamentals laid by Fedora's Immutable Desktops. Allow me to introduce uBlue; I know that I'll undersell it regardless, so I recommend you to check the provided link instead.
-
Am I better off running a GNU/Linux distro over ChromeOS? If so, why?
the immutable desktops offered by Fedora; which would be Silverblue, Kinoite and Sericea (special mention goes to uBlue)
- lustris incompatible with mesa-freeworld?
-
[Qtile] stacking+tiling working setup, rewrote default widgets, my first rice
OS: Fedora Silverblue
- best distro for gaming with proton?
What are some alternatives?
ostree - Operating system and container binary deployment and upgrades
distrobox - Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available at: https://gitlab.com/89luca89/distrobox
chromium - The official GitHub mirror of the Chromium source
ublue - A familiar(ish) Ubuntu desktop for Fedora Silverblue.
rkt
windows-defender-remover - A tool which is uses to remove Windows Defender in Windows 8.x, Windows 10 (every version) and Windows 11.
eget - Easily install prebuilt binaries from GitHub.
ponysay - Pony rewrite of cowsay.
singularity - SingularityCE is the Community Edition of Singularity, an open source container platform designed to be simple, fast, and secure.
AppImageKit - Package desktop applications as AppImages that run on common Linux-based operating systems, such as RHEL, CentOS, openSUSE, SLED, Ubuntu, Fedora, debian and derivatives. Join #AppImage on irc.libera.chat
knit - A simple and flexible build tool using Lua, similar to make/mk.