Group: Software/FSDG distributions/DistroExecutionEnvironments

From LibrePlanet
Jump to: navigation, search
(→‎Virtual execution environments availability in FSDG compliant distributions: Add dragora)
(→‎Virtual execution environments availability in FSDG compliant distributions: Add Guix shell.)
 
(10 intermediate revisions by 2 users not shown)
Line 25: Line 25:
 
== Running distributions in a virtual execution environments ==
 
== Running distributions in a virtual execution environments ==
  
−
Here some known working combinaison of distributions and virtual execution environments:
+
This answer the question "Can <distribution> run inside <execution environment>", which typically runs on another distribution.
 +
 
 +
The table below only lists maintained distributions. See [[Group:Software/FSDG_distributions/UnmaintainedDistroVersions|UnmaintainedDistroVersions]] for issues you may face when running unmaintained versions of free distributions or how to do it.
  
 
{| class="wikitable"  border="1"
 
{| class="wikitable"  border="1"
 
| colspan=2 rowspan=2 |
 
| colspan=2 rowspan=2 |
−
! colspan=8 | Distributions
+
! colspan=7 | Distributions (that are maintained)
 
|-    <!-- All the distributions are listed below -->
 
|-    <!-- All the distributions are listed below -->
 +
! Dragora 3.0-beta2
 
! Guix
 
! Guix
 
! Hyperbola
 
! Hyperbola
Line 36: Line 39:
 
! PureOS
 
! PureOS
 
! Replicant
 
! Replicant
−
! Trisquel 8.0 (Flidas)
 
−
! Trisquel 9.0 (etiona)
 
 
! Trisquel 10 (nabia)
 
! Trisquel 10 (nabia)
 
|-
 
|-
−
! rowspan=3 | Runtimes
+
! rowspan=4 | Runtimes
 +
! Guix shell
 +
| {{no}}
 +
| {{yes}}
 +
| {{no}}
 +
| {{no}}
 +
| {{no}}
 +
| {{no}}
 +
| {{no}}
 +
 
 +
|-
 
! libvirt's LXC
 
! libvirt's LXC
 +
| ?
 
| {{No}}<ref name="guix-lxc-block-device">'''guix system''' cannot produce a chroot in a directory if it's not backed by a block device.</ref><ref name="guix-lxc-startup">'''guix system init''' doesn't have an easy way for the host to know which init binary to run which which arguments.</ref>
 
| {{No}}<ref name="guix-lxc-block-device">'''guix system''' cannot produce a chroot in a directory if it's not backed by a block device.</ref><ref name="guix-lxc-startup">'''guix system init''' doesn't have an easy way for the host to know which init binary to run which which arguments.</ref>
 
| {{Yes}}
 
| {{Yes}}
Line 47: Line 59:
 
| {{Yes}}
 
| {{Yes}}
 
| {{no}}<ref name="replicant-virt">Nobody tried to run Replicant in a vm or container.</ref>
 
| {{no}}<ref name="replicant-virt">Nobody tried to run Replicant in a vm or container.</ref>
−
| {{no}}<ref name="trisquel-8-lxc">At the time of writing (May 2021) Trisquel 8 doesn't work anymore in LXC through libvirt in Parabola:
 
−
Failed to create symlink /sys/fs/cgroup/net_cls: Operation not permitted
 
−
Freezing execution.
 
−
 
−
This is due to [https://bugzilla.redhat.com/show_bug.cgi?id=1770763 a cgroup API change].
 
−
 
−
However Trisquel 9 works fine in this context and Trisquel 8 is not supported anymore by Trisquel since April 2021.</ref>
 
−
| {{Yes}}
 
 
| {{Yes}}
 
| {{Yes}}
 
|-
 
|-
 
! Qemu / Qemu KVM / Bare metal
 
! Qemu / Qemu KVM / Bare metal
 +
| {{Yes}}
 
| {{Yes}}
 
| {{Yes}}
 
| {{Yes}}
 
| {{Yes}}
Line 63: Line 68:
 
| {{Yes}}
 
| {{Yes}}
 
| {{no}}<ref name="replicant-virt"></ref>
 
| {{no}}<ref name="replicant-virt"></ref>
−
| {{Yes}}
 
−
| {{Yes}}
 
 
| {{Yes}}
 
| {{Yes}}
 
|-
 
|-
 
! Docker<ref>This references if it's possible to create docker images for a given distribution. For (the lack of) FSDG compliant docker registries and possible workarounds, see the [[Group:Software/research/ExternalRepositories#Docker_registries|ExternalRepositories]] page.</ref>
 
! Docker<ref>This references if it's possible to create docker images for a given distribution. For (the lack of) FSDG compliant docker registries and possible workarounds, see the [[Group:Software/research/ExternalRepositories#Docker_registries|ExternalRepositories]] page.</ref>
 +
| ?
 
| {{Yes}}<ref>An image can be produced with the 'guix system image -t docker system.scm' command. Guix can also be installed on top of most GNU/Linux and GNU/Hurd distributions.</ref>
 
| {{Yes}}<ref>An image can be produced with the 'guix system image -t docker system.scm' command. Guix can also be installed on top of most GNU/Linux and GNU/Hurd distributions.</ref>
 
| {{no}}<ref>I found no hyperbola docker package, no docker related git repository in [https://git.hyperbola.info:50100/ git.hyperbola.info], and while parabola-docker has very few parabola specific files, [https://git.parabola.nu/~lukeshu/parabola-docker.git/tree/rootfs/etc/pacman.d/mirrorlist very few it has at least one], so hyperbola support probably need to be added in the parabla-docker program. Though Hyperbola is also switching to a BSD kernel, so docker might not work anymore there. So there might not be enough interest to do that.</ref>
 
| {{no}}<ref>I found no hyperbola docker package, no docker related git repository in [https://git.hyperbola.info:50100/ git.hyperbola.info], and while parabola-docker has very few parabola specific files, [https://git.parabola.nu/~lukeshu/parabola-docker.git/tree/rootfs/etc/pacman.d/mirrorlist very few it has at least one], so hyperbola support probably need to be added in the parabla-docker program. Though Hyperbola is also switching to a BSD kernel, so docker might not work anymore there. So there might not be enough interest to do that.</ref>
−
| {{orange|yes, Not packaged, requires Parabola.}}<ref>[https://git.parabola.nu/~lukeshu/parabola-docker.git/tree/README.md A project] exist to build Parabola docker images but it's not packaged in Parabola</ref>
+
| {{orange|yes, Not packaged, requires Parabola to create the docker container.}}<ref>[https://git.parabola.nu/~lukeshu/parabola-docker.git/tree/README.md A project] exist to build Parabola docker images but it's not packaged in Parabola</ref>
−
| {{orange|yes, with configuration. Requires debuerreotype with recent debootstrap.}}<ref name="pureos-debuerreotype">PureOS has [https://repo.pureos.net/pureos/pool/main/d/debuerreotype/debuerreotype_0.10-2_all.deb a package for debuerreotype], the software used to create the semi-official Debian images on docker.com. It uses debootstrap so it can create PureOS images. However the package documentation mention Ubuntu or Debian examples, so someone needs to bugreport and/or fix it. The  '''debuerreotype-init --non-debian rootfs amber https://repo.pureos.net/pureos''' command can be used to create a PureOS rootfs on PureOS. There is also some [https://tracker.pureos.net/w/development/pureos_docker_images/ documentation] on how to do that the PureOS wiki.</ref>
+
| {{orange|yes, with configuration. Requires debuerreotype with a recent debootstrap to create the docker container.}}<ref name="pureos-debuerreotype">PureOS has [https://repo.pureos.net/pureos/pool/main/d/debuerreotype/debuerreotype_0.10-2_all.deb a package for debuerreotype], the software used to create the semi-official Debian images on docker.com. It uses debootstrap so it can create PureOS images. However the package documentation mention Ubuntu or Debian examples, so someone needs to bugreport and/or fix it. The  '''debuerreotype-init --non-debian rootfs amber https://repo.pureos.net/pureos''' command can be used to create a PureOS rootfs on PureOS. There is also some [https://tracker.pureos.net/w/development/pureos_docker_images/ documentation] on how to do that the PureOS wiki.</ref>
 
| {{no}}<ref name="replicant-virt"></ref>
 
| {{no}}<ref name="replicant-virt"></ref>
−
| ?
+
| {{orange|yes, with configuration, Requires debuerreotype with recent Trisquel 9 or 10 to create the docker container.}}<ref name="trisquel-debuerreotype">[https://packages.trisquel.org/flidas/debuerreotype Trisquel 9] and [https://packages.trisquel.org/nabia/debuerreotype Trisquel 10] have a package for debuerreotype, the software used to create the semi-official Debian images on docker.com. It uses debootstrap so it can create Trisquel images. However the package documentation mention Ubuntu or Debian examples, so someone needs to bugreport and/or fix it. The  '''debuerreotype-init --non-debian rootfs nabia http://archive.trisquel.info/trisquel''' command can be used to create a Trisquel 10 rootfs on Trisquel 10.</ref>
−
| {{orange|yes, with configuration, Requires debuerreotype with recent Trisquel 9 or 10.}}<ref name="trisquel-debuerreotype">[https://packages.trisquel.org/flidas/debuerreotype Trisquel 9] and [https://packages.trisquel.org/nabia/debuerreotype Trisquel 10] have a package for debuerreotype, the software used to create the semi-official Debian images on docker.com. It uses debootstrap so it can create Trisquel images. However the package documentation mention Ubuntu or Debian examples, so someone needs to bugreport and/or fix it. The  '''debuerreotype-init --non-debian rootfs nabia http://archive.trisquel.info/trisquel''' command can be used to create a Trisquel 10 rootfs on Trisquel 10.</ref>
 
−
| {{orange|yes, with configuration, Requires debuerreotype with recent Trisquel 9 or 10.}}<ref name="trisquel-debuerreotype"></ref>
 
 
|}
 
|}
  
 
== Virtual execution environments availability in FSDG compliant distributions ==
 
== Virtual execution environments availability in FSDG compliant distributions ==
 +
 +
This answer the question "Does <distribution> has <execution environment>" to run things like other distributions inside.
  
 
{| class="wikitable"  border="1"
 
{| class="wikitable"  border="1"
Line 89: Line 93:
 
! PureOS 10.0 (byzantium)
 
! PureOS 10.0 (byzantium)
 
! Trisquel 10 (nabia)
 
! Trisquel 10 (nabia)
 +
! Trisquel 11 (aramo)
 
! Ututo S
 
! Ututo S
 
|-
 
|-
Line 99: Line 104:
 
| {{yes}}<ref>PureOS has the docker.io package and it works fine.</ref>
 
| {{yes}}<ref>PureOS has the docker.io package and it works fine.</ref>
 
| {{yes}}<ref>The [https://packages.trisquel.org/nabia/docker.io Trisquel docker.io package] has a docker service that can be activated.</ref>
 
| {{yes}}<ref>The [https://packages.trisquel.org/nabia/docker.io Trisquel docker.io package] has a docker service that can be activated.</ref>
 +
| {{yes}}<ref>Tested with a docker postgresql docker container made with Guix</ref>.
 +
|
 +
|-
 +
! Guix shell
 +
| {{no}}<ref>No packages, can be installed but if you use the guix-installer script it will require the patch in the bug [https://debbugs.gnu.org/cgi/bugreport.cgi?bug=72514 bug #72514] to start the Guix daemon.</ref>
 +
|
 +
| {{yes}}
 +
|  {{no}}<ref name="guix-manual-install-untested">There is no package. But it can probably [https://guix.gnu.org/manual/en/guix.html#Installation be installed manually]. Someone needs to test that procedure though.</ref>
 +
| {{yes}}
 +
| {{yes}}
 +
| {{no}}<ref name="guix-manual-install">There is no package so it can [https://guix.gnu.org/manual/en/guix.html#Installation be installed manually].</ref>
 +
| {{yes}}
 +
|
 
|-
 
|-
 
! Libvirt LXC
 
! Libvirt LXC
Line 108: Line 126:
 
|
 
|
 
| ?
 
| ?
 +
| {{yes}}<ref>I can connect to libvirt-lxc in virt-manager.</ref>
 
|
 
|
 
|-
 
|-
Line 118: Line 137:
 
|
 
|
 
| {{yes}}
 
| {{yes}}
 +
| {{yes}}<ref>I can connect to libvirt-qemu in virt-manager. Also deployed in production in Libre En Communs infrastructure.</ref>
 +
|
 
|-
 
|-
 
! Libvirt Xen
 
! Libvirt Xen
Line 127: Line 148:
 
|
 
|
 
| ?
 
| ?
 +
| {{yes}}<ref>I can connect to libvirt-xen in virt-manager after installing xen-system-amd64, libvirt-daemon-driver-xen libvirt-daemon, virt-manager, and adding my user to the libvirt group. Note that I had to use a computer with a nonfree BIOS to do these tests as I didn't really manage to get GNU Boot working with Xen reliabily enough.</ref>
 
|
 
|
 
|}
 
|}

Latest revision as of 08:12, 4 October 2024

Introduction

The Free System Distribution Guidelines (GNU FSDG) have the following: 

Complete Distros

Our list of distributions is a guide for systems you can install in a computer. Therefore, it only includes distributions that are complete in themselves and ready to use. [...]

An exception to this requirement and to the self-hosting requirement above is for small system distributions, which are distros designed for devices with limited resources, like a wireless router for example. Free small system distributions do not need to be self-hosting or complete, because it is impractical to do development on such a system, but it must be developable and buildable on top of a free complete system distribution from our list of distributions, perhaps with the aid of free tools distributed alongside the small system distribution itself.

So sometimes (like with Replicant) building the small distribution rely on being able to install specific FSDG compliant distributions.

So for instance building Replicant has only been tested on specific distributions (typically Trisquel), so if you run another FSDG distribution (like Parabola for instance) you might want to run Trisquel under Parabola somehow.

Other uses cases could be to deploy services that is packaged in a distribution and not another.

For instance Freedombox is in PureOS and in Trisquel but not in Parabola or Guix.

Installing

There are often various possibilities for installing an FSDG distribution in a virtual environment. For instance

  • You can cross bootstrap it (see the CrossDistroBootstrap article for more details)
  • You can also install in a VM that emulates a complete computer like Qemu with KVM.

Running distributions in a virtual execution environments

This answer the question "Can <distribution> run inside <execution environment>", which typically runs on another distribution.

The table below only lists maintained distributions. See UnmaintainedDistroVersions for issues you may face when running unmaintained versions of free distributions or how to do it.

Distributions (that are maintained)
Dragora 3.0-beta2 Guix Hyperbola Parabola PureOS Replicant Trisquel 10 (nabia)
Runtimes Guix shell No Yes No No No No No
libvirt's LXC ? No[1][2] Yes Yes Yes No[3] Yes
Qemu / Qemu KVM / Bare metal Yes Yes Yes Yes Yes No[3] Yes
Docker[4] ? Yes[5] No[6] yes, Not packaged, requires Parabola to create the docker container.[7] yes, with configuration. Requires debuerreotype with a recent debootstrap to create the docker container.[8] No[3] yes, with configuration, Requires debuerreotype with recent Trisquel 9 or 10 to create the docker container.[9]

Virtual execution environments availability in FSDG compliant distributions

This answer the question "Does <distribution> has <execution environment>" to run things like other distributions inside.

Distribution Dragora Dynebolic Guix Hyperbola Parabola PureOS 10.0 (byzantium) Trisquel 10 (nabia) Trisquel 11 (aramo) Ututo S
Docker No[10] Yes[11] No[12] Yes[13] Yes[14] Yes[15] Yes[16].
Guix shell No[17] Yes No[18] Yes Yes No[19] Yes
Libvirt LXC No[20] Yes[21] No[22] Yes[23] ? Yes[24]
Libvirt qemu-kvm No[20] Yes No[22] Yes Yes Yes[25]
Libvirt Xen No[20] No[26] No[22] No[27] ? Yes[28]

Other execution environment

Host software name Host software FSDG status Target FSDG compliant programs exist?
DOSBox OK Yes[29]
MAME Yes
  • Present in many FSDG comlpiant distributions
  • Not reviewed yet by the Free Software Directory
 Yes[30]
Retroarch Yes
  • Present in many FSDG comlpiant distributions
  • Not reviewed yet by the Free Software Directory
 Yes Has some backends that are OK:
Qemu + SeaBIOS Yes
  • Reviewed by the Free Software Directory
  • Packaged most FSDG compliant distros
 Yes[32]
Qemu + Tianocore Yes
  • Tianocore not yet reviewed by the Free Software Directory
  • Packaged most FSDG compliant distros[33]
Yes[34]
Uzem OK Yes[35]
Wine
  • OK in FSDG compliant distributions.
  • Some other distributions automatically install nonfree fonts with wine.[36]
Yes[37]

See also

References

  1. ↑ guix system cannot produce a chroot in a directory if it's not backed by a block device.
  2. ↑ guix system init doesn't have an easy way for the host to know which init binary to run which which arguments.
  3. ↑ 3.03.13.2 Nobody tried to run Replicant in a vm or container.
  4. ↑ This references if it's possible to create docker images for a given distribution. For (the lack of) FSDG compliant docker registries and possible workarounds, see the ExternalRepositories page.
  5. ↑ An image can be produced with the 'guix system image -t docker system.scm' command. Guix can also be installed on top of most GNU/Linux and GNU/Hurd distributions.
  6. ↑ I found no hyperbola docker package, no docker related git repository in git.hyperbola.info, and while parabola-docker has very few parabola specific files, very few it has at least one, so hyperbola support probably need to be added in the parabla-docker program. Though Hyperbola is also switching to a BSD kernel, so docker might not work anymore there. So there might not be enough interest to do that.
  7. ↑ A project exist to build Parabola docker images but it's not packaged in Parabola
  8. ↑ PureOS has a package for debuerreotype, the software used to create the semi-official Debian images on docker.com. It uses debootstrap so it can create PureOS images. However the package documentation mention Ubuntu or Debian examples, so someone needs to bugreport and/or fix it. The debuerreotype-init --non-debian rootfs amber https://repo.pureos.net/pureos command can be used to create a PureOS rootfs on PureOS. There is also some documentation on how to do that the PureOS wiki.
  9. ↑ Trisquel 9 and Trisquel 10 have a package for debuerreotype, the software used to create the semi-official Debian images on docker.com. It uses debootstrap so it can create Trisquel images. However the package documentation mention Ubuntu or Debian examples, so someone needs to bugreport and/or fix it. The debuerreotype-init --non-debian rootfs nabia http://archive.trisquel.info/trisquel command can be used to create a Trisquel 10 rootfs on Trisquel 10.
  10. ↑ Dragora doesn't have any docker package.
  11. ↑ There is a docker package and service
  12. ↑ Hyperbola doesn't have any docker package: https://www.hyperbola.info/packages/?sort=&q=docker
  13. ↑ The Parabola docker package has a docker service that can be activated.
  14. ↑ PureOS has the docker.io package and it works fine.
  15. ↑ The Trisquel docker.io package has a docker service that can be activated.
  16. ↑ Tested with a docker postgresql docker container made with Guix
  17. ↑ No packages, can be installed but if you use the guix-installer script it will require the patch in the bug bug #72514 to start the Guix daemon.
  18. ↑ There is no package. But it can probably be installed manually. Someone needs to test that procedure though.
  19. ↑ There is no package so it can be installed manually.
  20. ↑ 20.020.120.2 Dragora doesn't have any libvirt package.
  21. ↑ Tested with Guix x86_64-linux and Trisquel 11 x86_64 and Parabola
  22. ↑ 22.022.122.2 Hyperbola doesn't have any libvirt package: https://www.hyperbola.info/packages/?sort=&q=libvirt
  23. ↑ Tested with Parabola, Trisquel 9, Trisquel 10 and other distributions.
  24. ↑ I can connect to libvirt-lxc in virt-manager.
  25. ↑ I can connect to libvirt-qemu in virt-manager. Also deployed in production in Libre En Communs infrastructure.
  26. ↑ Guix's libvirt seems not to be built with Xen
  27. ↑ libvirt is not built with Xen support in the libvirt package (which comes from Arch Linux).
  28. ↑ I can connect to libvirt-xen in virt-manager after installing xen-system-amd64, libvirt-daemon-driver-xen libvirt-daemon, virt-manager, and adding my user to the libvirt group. Note that I had to use a computer with a nonfree BIOS to do these tests as I didn't really manage to get GNU Boot working with Xen reliabily enough.
  29. ↑ COMMAND.com is a program shipped by DOSBox and it's being built with it. Since FSDG compliant distributions ship DOSBox, they probably also build it along the way.
  30. ↑ There is a tutorial on how to launch and/or convert uzebox games to be used with MAME but not all of the game work. DrMario was tested with the same git revision used in the Free software directory and seemed to work. To build it for MAME: $ git clone https://github.com/Uzebox/uzebox
    $ cd uzebox
    $ git checkout e05013c91a77dc32a541f692c82d91250035d66f
    $ make -C tools/packrom/
    $ export PATH=$PATH:$PWD/tools/packrom/
    $ cd demos/DrMario/default
    $ make
    $ objcopy -I ihex DrMario.hex -O binary dr-mario.bin
    Then get where the rom directory is located:
    $ mame -showconfig | grep '^rompath'
    rompath $HOME/mame/roms
    Then install the dr-mario.bin in a uzeboz directory in the rom directory:
    $ mkdir -p $HOME/mame/roms/uzebox
    $ mv dr-mario.bin $HOME/mame/roms/uzebox/
    And we finally I run drmario like that, with the Guix MAME under Parabola:
    $ mame uzebox drmario
    dr-mario.bin WRONG LENGTH (expected: 0000dcaa found: 0000ce5a)
    dr-mario.bin WRONG CHECKSUMS:
    EXPECTED: CRC(8144b271) SHA1(d4bb13f54b756e2ba9e57075aae473b72397f48f)
    FOUND: CRC(c0130ccf) SHA1(8bca126a623c19033eace513ae547a0560e9f558)
    WARNING: the machine might not run correctly.
    Average speed: 41.13% (3 seconds)
    And that showed a game on the screen. Pressing 1 make it does stuff, but I'm not sure what the controls are.
  31. ↑ "Some cores, like 2048, do not require any content in order to work": https://www.retroarch.com/?page=cores
  32. ↑ Example: The installer image of most FSDG compliant distributions supporting i686 or x86_64
  33. ↑ For Tianocore in Parabola the package is named edk2-ovmf
  34. ↑ Example: The installer image of most FSDG compliant distributions supporting x86_64
  35. ↑ Uzem, packrom and Arkanoid were checked directly with their upstream source code at the same git version that was reviewed on the Free Software Directory, with Parabola x86_64 and avr-gcc and avr-libc installed:
    $ git clone https://github.com/Uzebox/uzebox
    $ cd uzebox
    $ git checkout e05013c91a77dc32a541f692c82d91250035d66f
    $ make -C tools/uzem/
    $ make -C tools/packrom/
    $ export PATH=$PATH:$PWD/tools/packrom/
    $ cd demos/Arkanoid/default
    $ make
    $ make Arkanoid.uze
    Then running the emulator on the game we built also works fine:
    $ ../../../tools/uzem/uzem Arkanoid.uze
    We have the game graphics appearing inside the emulator and so on.
  36. ↑ Reference: https://directory.fsf.org/wiki/Wine
  37. ↑ GNU Hello can be built with Guix and run in Parabola (with Parabola's wine) with the following command:
    $ wine $(guix build --target=x86_64-w64-mingw32 hello)/bin/hello.exe
    [...]
    Hello, world!
    It is also possible build and run more useful programs like xz in the same way, though not many programs are known to cross compile well. People can also contribute to Guix to make more program cross compile and/or to package free software for windows and run that with Wine.
Retrieved from "https://libreplanet.org/wiki?title=Group:Software/FSDG_distributions/DistroExecutionEnvironments&oldid=70447"