http://fsquillace.github.io/junest-site/ JuNest Linux Logo The lightweight Arch Linux based distro that runs upon any Linux distros without root access. * Home * Getting Started * Documentation * Community * About * View in Github JuNest The lightweight Arch Linux based distro that runs upon any Linux distros without root access. Star Project Donation Communication Status Build Join the gitter chat at https://gitter.im/fsquillace status PayPal /junest Join the IRC chat at https:// OpenHub Gratipay webchat.freenode.net/?channels=junest Join the group at https://groups.google.com/d/forum/junest RSS Description JuNest (Jailed User NEST) is a lightweight Arch Linux based distribution that allows to have an isolated GNU/Linux environment inside any generic host GNU/Linux OS and without the need to have root privileges for installing packages. JuNest contains mainly the package managers (called pacman and a simple yaourt wrapper called yogurt) that allows to access to a wide range of packages from the Arch Linux repositories. The main advantages on using JuNest are: * Install packages without root privileges. * Partial isolated environment which you can install packages without affecting a production system. * Access to a wide range of packages in particular on GNU/Linux distros that may contain limited repositories (such as CentOS and RedHat). * Available for x86_64, x86 (deprecating) and ARM architectures but you can build your own image from scratch too! * Run on a different architecture from the host OS via QEMU * All Arch Linux lovers can have their favourite distro everywhere! JuNest follows the Arch Linux philosophy. How different is JuNest from Docker and Vagrant? Although JuNest sounds similar to a virtualisation/Linux container -like system, JuNest differentiate a lot between Docker and Vagrant. In fact, the purpose of JuNest is not to build a complete isolated environment but, conversely, is the ability to run programs as they were running natively from the host OS. Almost everything is shared between host OS and the JuNest sandbox (kernel, process subtree, network, mounting, etc) and only the root filesystem gets isolated (as the programs installed in JuNest need to reside elsewhere). This allows interaction between processes belonging to both host OS and JuNest. For instance, you can install top command in JuNest in order to monitor any processes belonging to the host OS. Blog posts RSS feed RSS feedly * 18 Oct 2017 >> 3rd JuNest birthday * 14 Oct 2017 >> Poor support for PRoot backend * 14 Oct 2017 >> Phasing out support for JuNest x86 * 18 Apr 2017 >> New JuNest 6.0.0 * 12 Mar 2016 >> JuNest and Travis CI * 25 Oct 2015 >> New JuNest 5.6.7! * 23 Oct 2015 >> JuNest and Systemd * 09 Aug 2015 >> JuNest is now in AUR! * 29 Jun 2015 >> JuNest on different architectures * 22 Jun 2015 >> Welcome to jchroot! * 20 Jun 2015 >> JuNest runs on exotic environments * 18 Oct 2014 >> Everything starts from zero! (MUST READ)