Test repo for the Atomic Desktops
Find a file
Tomas Popela 1c18c45417 comps-sync rawhide 06-03-2019
./comps-sync.py ../fedora-comps/comps-f31.xml.in --save
Syncing packages common to all desktops:
  - All manifest packages are already listed in comps.
  - 1 packages not in manifest:
    zram (mandatory, groups: workstation-product)
Wrote fedora-common-ostree-pkgs.yaml

Syncing packages for gnome-desktop:
  - All manifest packages are already listed in comps.
  - 1 packages not in gnome-desktop manifest:
    orca
Wrote gnome-desktop-pkgs.yaml

Syncing packages for kde-desktop:
  - All manifest packages are already listed in comps.
  - All comps packages are already listed in manifest.

Syncing packages for xfce-desktop:
  - 1 packages not in xfce-desktop comps group:
    xfce4-session-engines
  - All comps packages are already listed in manifest.
Wrote xfce-desktop-pkgs.yaml

Syncing packages for lxqt-desktop:
  - All manifest packages are already listed in comps.
  - All comps packages are already listed in manifest.

Syncing packages for deepin-desktop:
  - All manifest packages are already listed in comps.
  - All comps packages are already listed in manifest.

Syncing packages for pantheon-desktop:
  - All manifest packages are already listed in comps.
  - All comps packages are already listed in manifest.
2019-07-22 12:34:49 +02:00
comps-sync-blacklist.yml Include orca in the Silverblue 2019-07-22 12:34:21 +02:00
comps-sync.py comps-sync: Blacklist PackageKit globally 2019-04-13 12:26:22 +00:00
config.ini
deepin-desktop-pkgs.yaml Add Pantheon & DeepinDE variants 2019-04-07 14:22:26 +02:00
fedora-common-ostree-pkgs.yaml comps-sync rawhide 06-03-2019 2019-07-22 12:34:49 +02:00
fedora-common-ostree.yaml Blacklist x86_64 specific packages and make them arch specific 2019-05-07 20:39:27 +02:00
fedora-deepin.yaml Add Pantheon & DeepinDE variants 2019-04-07 14:22:26 +02:00
fedora-kinoite.yaml Add some minor comments 2019-04-07 13:41:24 +02:00
fedora-lxqt.yaml Add some minor comments 2019-04-07 13:41:24 +02:00
fedora-pantheon.yaml Add Pantheon & DeepinDE variants 2019-04-07 14:22:26 +02:00
fedora-rawhide.repo
fedora-silverblue.yaml Move packages needed for all variants to common manifest 2019-04-07 13:41:06 +02:00
fedora-xfce.yaml Convert all remaining json manifests to yaml 2019-04-07 13:41:06 +02:00
gnome-desktop-pkgs.yaml comps-sync rawhide 06-03-2019 2019-07-22 12:34:49 +02:00
group
kde-desktop-pkgs.yaml comps-blacklist: keep one browser and file manager 2019-04-16 00:04:17 +02:00
lxqt-desktop-pkgs.yaml comps-blacklist: keep one browser and file manager 2019-04-16 00:04:17 +02:00
pantheon-desktop-pkgs.yaml comps-sync f31 2019-04-13 2019-04-15 23:44:53 +02:00
passwd
post.sh
README.md README.md: point to Silverblue docs 2019-02-28 09:18:58 -05:00
xfce-desktop-pkgs.yaml comps-sync rawhide 06-03-2019 2019-07-22 12:34:49 +02:00

For some background, see:

(Note also this repo obsoletes https://pagure.io/atomic-ws)

High level design

The goal of the system is to be a workstation, using rpm-ostree for the base OS, and a combination of Docker and Flatpak containers, as well as virtualization tools such as Vagrant.

Status

This project is actively maintained and is ready for use by sophisticated and interested users, but not ready for widespread promotion.

See some [https://lists.fedoraproject.org/archives/list/desktop@lists.fedoraproject.org/thread/J6BJS7Z4NKNOQUZWGYXZZIEKYMWBBSUY/](discussion about the first release).

Installing

See the Silverblue documentation at https://docs.fedoraproject.org/en-US/fedora-silverblue/installation-guide/. There's also a guide for installing inside an existing system: https://docs.fedoraproject.org/en-US/fedora-silverblue/installation-dual-boot/.

Important issues:

Using the system

One of the first things you should do use is use a container runtime of your choice to manage one or more "pet" containers. This is where you will use yum/dnf to install utilities.

With docker for example, you can use the -v /srv:/srv command line option so these containers can share content with your host (such as git repositories). Note that if you want to share content between multiple Docker containers and the host (e.g. your desktop session), you should execute (once):

sudo chcon -R -h -t container_file_t /var/srv

Next, let's try flatpak. Before you do: There's a known flatpak issue on AtomicWS - run this workaround, which you only need to do once. After that, try flatpak.

If you are a developer for server applications, try oc cluster up to create a local OpenShift v3 cluster.

Finally, try out rpm-ostree install to layer additional packages directly on the host. This is needed for "host extensions" - privileged software that doesn't make sense to live in a container. For example, rpm-ostree install powerline to use that software for the shell prompts of the host. Another good example is rpm-ostree install vagrant-libvirt to use Vagrant to manage VMs.

Future work

  • GNOME Software support for both rpm-ostree/flatpak and possibly docker
  • automated tests that run on this content