No description
Find a file
Timothée Ravier 7c611d9d0d Convert all remaining json manifests to yaml
This conversion can be validated using this script:

 #!/bin/bash

mkdir -p repo && cd repo && ostree init --repo . --mode=archive && cd ..
variants=('silverblue' 'kinoite' 'xfce' 'lxqt')

for v in ${variants[@]}; do
    sudo rpm-ostree compose tree --repo=repo --print-only fedora-$v.yaml > $v.yaml.out
done

git checkout --quiet HEAD~
for v in ${variants[@]}; do
    sudo rpm-ostree compose tree --repo=repo --print-only fedora-$v.yaml > $v.json.out
done

for v in ${variants[@]}; do
    if [[ ! -z $(diff $v.json.out $v.yaml.out) ]]; then
        echo ""
        echo "$v: JSON != YAML"
        diff $v.json.out $v.yaml.out
        echo ""
        has_diff="true"
    fi
done

git checkout --quiet master
rm -rf ./repo
for v in ${variants[@]}; do
    rm ./$v.json.out ./$v.yaml.out
done

if [[ $has_diff == "true" ]]; then
    echo "Found some diff!"
else
    echo "OK!"
fi
2019-04-07 13:41:06 +02:00
comps-sync-blacklist.yml Add LXQt variant 2019-03-21 09:14:57 +01:00
comps-sync.py comps-sync.py: remove unused varaibles and minor renaming 2019-04-07 12:41:05 +02:00
config.ini use download.fp.o to download content from 2016-09-18 21:06:44 -05:00
fedora-common-ostree-pkgs.yaml Convert all remaining json manifests to yaml 2019-04-07 13:41:06 +02:00
fedora-common-ostree.yaml Convert all remaining json manifests to yaml 2019-04-07 13:41:06 +02:00
fedora-kinoite.yaml Convert all remaining json manifests to yaml 2019-04-07 13:41:06 +02:00
fedora-lxqt.yaml Convert all remaining json manifests to yaml 2019-04-07 13:41:06 +02:00
fedora-rawhide.repo Revert "Branching f27 from rawhide" 2017-09-11 10:58:44 -04:00
fedora-silverblue.yaml Convert all remaining json manifests to yaml 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 Convert all remaining json manifests to yaml 2019-04-07 13:41:06 +02:00
group Initial commit 2016-04-05 08:39:25 +02:00
kde-desktop-pkgs.yaml Convert all remaining json manifests to yaml 2019-04-07 13:41:06 +02:00
lxqt-desktop-pkgs.yaml Convert all remaining json manifests to yaml 2019-04-07 13:41:06 +02:00
passwd Initial commit 2016-04-05 08:39:25 +02:00
post.sh post: Disable modular repositories 2018-09-09 09:04:48 -04:00
README.md README.md: point to Silverblue docs 2019-02-28 09:18:58 -05:00
xfce-desktop-pkgs.yaml Convert all remaining json manifests to yaml 2019-04-07 13:41:06 +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