{"id":118557,"date":"2024-07-29T15:43:12","date_gmt":"2024-07-29T13:43:16","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/reliz-distributiva-vanilla-os-2-ispolzuyushhego-kontejnery-i-atomarnye-obnovleniya"},"modified":"2024-07-29T15:43:12","modified_gmt":"2024-07-29T13:43:16","slug":"reliz-distributiva-vanilla-os-2-ispolzuyushhego-kontejnery-i-atomarnye-obnovleniya","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/reliz-distributiva-vanilla-os-2-ispolzuyushhego-kontejnery-i-atomarnye-obnovleniya","title":{"rendered":"Release of Vanilla OS 2 distribution, using containers and atomic updates","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

After a year and a half of development, the user distribution release of Vanilla OS 2 has been published, based on a Debian package base but going beyond a standard rebuild. The system environment in Vanilla OS is mounted in read-only mode and updated atomically, while applications run in separate containers, utilizing a layer based on the Distrobox toolkit. The user environment features an unmodified GNOME, provided in the form in which it is originally released by the developers. Custom graphical configuration tools are written in GTK4 using Libadwaita. The size of the ISO image is 1.62 GB. <\/p>\n

To ensure atomic updates, the project is developing the ABRoot toolkit, which creates two identical root partitions on the storage \u2014 active and passive. The system update is fully downloaded and installed in the passive partition, and after a reboot, the partitions swap places \u2014 the partition with the installed update becomes active, while the previously active partition switches to passive mode, waiting for the next update installation. Updates are checked and installed automatically in the background during minimal system load and with sufficient battery charge. The update checking frequency is configurable. The installed update is activated upon the next reboot. If something goes wrong after the update, the system rolls back to the previous version.

\"Release<\/center> <\/p>\n

Additional applications are installed in separate containers using the custom package manager apx, which allows packages from different distributions to be installed in isolated sandbox environments (for example, packages from Debian, Ubuntu, Arch Linux, and Fedora can be installed). The package manager is implemented as a wrapper over the Distrobox toolkit, allowing for quick installation and launching of any Linux distribution in a container and ensuring its integration with the main system. The format of the container-based packages (Flatpak, Snap, or AppImage) is chosen at the first launch. <\/p>\n

The VSO (Vanilla System Operator) toolkit is being developed for system administration, allowing tasks such as system updates, configuration changes, and creating tasks linked to specific actions (for example, you can set up a task to display a notification after the battery has finished charging). It offers built-in capabilities to run Android applications using the Waydroid toolkit. <\/p>\n

In the new version: <\/p>\n