atomic-desktops/ci-test
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Test repo for the Atomic Desktops
120 commits 2 branches 0 tags 511 KiB
Just 50.3%
Python 49.7%
Find a file
Colin Walters 6d028cb372 comps: Strip more cmdline tools and also psacct 
I'm trying to do a `--unified-core` build in prep for rojig, and
it breaks on `psacct` which is trying to write to `/var`.  Let's
use this opportunity to do some more cleaning.
2018-07-31 00:05:19 +00:00
comps-sync-blacklist.yml comps: Strip more cmdline tools and also psacct 2018-07-31 00:05:19 +00:00
comps-sync.py comps-sync pass 3: Subset of workstation 2018-02-27 11:35:44 -05:00
config.ini
fedora-atomic-workstation.json Add flatpak-builder 2018-04-17 18:49:43 -04:00
fedora-ostree-workstation.json Split workstation-base from "atomic" 2018-02-12 12:12:25 -05:00
fedora-rawhide.repo
fedora-workstation-base-pkgs.json comps: Strip more cmdline tools and also psacct 2018-07-31 00:05:19 +00:00
fedora-workstation-base.json manifest: Set tmp-is-dir to enable tmpfs on /tmp 2018-03-26 12:15:10 -04:00
group
passwd
post.sh
README-install-inside.md README-install-inside.md: fix deployment text 2018-02-27 19:00:11 +00:00
README.md

README.md

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

There are ISOs available for Fedora 27.

Alternatively, see a guide for installing inside an existing system.

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