- Atomic Working Group (ARCHIVED) - Fedora mailing-lists

[atomic-wg] Issue #450: investigate coreos ignition for use in Fedora
by Dusty Mabe 05 Mar '19

05 Mar '19

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` CoreOS has a project called [ignition](https://github.com/coreos/ignition) that hooks into early boot processes in the initramfs (i.e. before and after the root filesystem is mounted) and allows for configuration of the system. This is an alternative to cloud-init, that is focused on specific tasks. Let's investigate this for Fedora and Atomic Host. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/450

7 7

Finally installed Atomic - I love it! - one question
by Philip Rhoades 18 Feb '19

18 Feb '19

People, I have been following Atomic for a long time and have been wanting to test it out but other dramas have kept me busy . . I usually have my latest machine as my Fedora Workstation and my previous workstation as my server for about a dozen small web sites and as a mail list server. I have finally gotten around to buliding a new workstation with F29 and turning the old WS into the F29 server. So now I have been able to use the old server as the new Atomic host and as a consolidated backup machine for all my old backup hard disks - mostly SATA but going back to IDE and one old SCSI backup that I had an early version of RH running on a 386. Atomic is just what I wanted for this backup machine - small and fast and a platform from which I can learn more about Atomic. I do have one question though: Could I make a dd image of the old SCSI drive and get it booting as a virtual machine on the Atomic machine? Many thanks for all the work that has gone into Project Atomic and I hope to learn much more about it in the future - including hosting my Rails and Jekyll Docker images . . Regards, Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: phil(a)pricom.com.au

2 2

Removing Atomic Host from Fedora Rawhide
by Dusty Mabe 15 Feb '19

15 Feb '19

Hello Fedora Atomic Host users, With the switched focus to Fedora CoreOS for the future of our immmutable, container oriented operating systems the last major release of Fedora Atomic Host was Fedora 29. Considering this we are removing the builds for Fedora Atomic Host from rawhide and will no longer be building that stream. If you are currently using Fedora Atomic Host on rawhide, please rebase to Fedora 29 so you'll continue to receive updates until Fedora 29 EOL. You can rebase with the command below. Please test this on some non-critical systems first. ``` rpm-ostree rebase fedora/29/x86_64/atomic-host ``` If you have trouble find me in #atomic or #fedora-coreos on freenode. Dusty

1 0

runc CVE-2019-5736 and Atomic Host
by Dusty Mabe 14 Feb '19

14 Feb '19

We are planning to do a release next week with updated versions of software that don't contain the exploit. We are not doing a release this week because there are two lines of defense that block this exploit on Atomic Host: 1. /usr/ is mounted read-only 2. SELinux is enabled by default SELinux blocks this exploit and /usr/ being read-only prevents the runc binary from being overwritten. Even if you had disabled SELinux /usr/ is still mounted read only so you're Atomic Host systems should be safe. Dusty https://nvd.nist.gov/vuln/detail/CVE-2019-5736

1 0

[atomic-wg] Issue #493: Kernel module support
by Joe Doss 18 Jan '19

18 Jan '19

jdoss reported a new issue against the project: `atomic-wg` that you are following: `` There seems at least one thread [1] on the mailing list that talks about getting kernel modules built on Atomic, but nothing that I could find has been created here to figure out the best path forward on supporting kernel modules. The use case that I am personally trying to fix is getting WireGuard working on Atomic. I maintain the RHEL/CentOS/Fedora Copr for WireGuard [2] and DKMS works pretty well for providing the WireGuard kernel module on non-atomic based installs. I have had some WireGuard users try and use the Copr RPMs on Atomic Host which resulted in failure. One of them was manually copying the .ko file over to get things working [3] and this isn't a really good solution long term. I now find myself in the same situation where I would like to use Wireguard on Atomic, so I am trying to figure out how to come up with a short term solution to this issue as the WireGuard devs work on getting WG pushed upstream into the mainline kernel. Even if that does happen somewhat soon, this problem will still impact others that need third party kernel modules working such as Nvidia drivers or third party monitoring services such as Sysdig [4] I started looking at creating a system container / systemd unit file that builds a new container on boot if a new kernel is detected. The current idea is it would do the following: 1) Check to see if a new kernel module is needed 2) Bind mount the `kernel-devel` source from the Atomic Host into the container 3) Check out the current WireGuard source and build the module (manually or via DKMS) 4) Enable's the newly built kernel module via system container [5] Some issues with this idea come to light quickly as the current Fedora Atomic Host snapshot has mismatching `kernel` and `kernel-devel` packages so building the module this way might not always work. I haven't fully figured out if this is the right path forward on getting kernel modules built. It seems that some folks have done somewhat similar things for CoreOS to get kernel module support for Nvidia based GPUs. [6] [7] I turned to IRC to get some pointers on my above idea to solve this problem and @walters recommended that I start an issue. [1] https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2017-Nov… [2] https://copr.fedorainfracloud.org/coprs/jdoss/wireguard/ [3] https://lists.zx2c4.com/pipermail/wireguard/2017-August/001656.html [4] https://sysdig.com/blog/dig-into-atomic-host/ [5] https://github.com/giuseppe/hellomod [6] https://github.com/ryanolson/CoreOS-GPU [6] https://github.com/src-d/coreos-nvidi7 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/493

3 3

Re: Fedora testing-20190116.0 compose check report
by Adam Williamson 16 Jan '19

16 Jan '19

On Wed, 2019-01-16 at 02:34 +0000, Fedora compose checker wrote: > No missing expected images. > > Failed openQA tests: 2/2 (x86_64) > > ID: 345338 Test: x86_64 AtomicHost-dvd_ostree-iso install_default@uefi > URL: https://openqa.fedoraproject.org/tests/345338 > ID: 345339 Test: x86_64 AtomicHost-dvd_ostree-iso install_default > URL: https://openqa.fedoraproject.org/tests/345339 Note - these mails should really go to the Atomic list (rather than test@ and devel@), but I need to update some things to make this happen (it worked when we had 'Fedora-Atomic' composes, but now those went away and we have these updates composes instead, it doesn't). It seems the Atomic installer images from the nightly 'updates' and 'updates-testing' composes for F29 started failing as of 20190115.n.0 and still failed in 20190116.n.0. Failure looks like: https://openqa.fedoraproject.org/tests/345339#step/_do_install_and_reboot/4 not sure what the cause is. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

2 1

[fedora-atomic] PR #114: add a few modules to initramfs to enable vmw/hyperv
by Dusty Mabe 21 Dec '18

21 Dec '18

dustymabe opened a new pull-request against the project: `fedora-atomic` that you are following: `` add a few modules to initramfs to enable vmw/hyperv `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/114

3 11

[atomic-wg] Issue #249: The build system should provide an automatically populated VERSION label
by Tomas Tomecek 22 Nov '18

22 Nov '18

ttomecek added a new comment to an issue you are following: `` I don't think there way any code written for this: https://github.com/projectatomic/atomic-reactor/issues/963 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/249

1 0

[atomic-wg] Issue #249: The build system should provide an automatically populated VERSION label
by Christian Glombek 21 Nov '18

21 Nov '18

lorbus added a new comment to an issue you are following: `` @cverna is this done now? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/249

1 0

[atomic-wg] Issue #339: Adding Fedora to AWS Marketplace
by David Duncan 21 Nov '18

21 Nov '18

davdunc reported a new issue against the project: `atomic-wg` that you are following: `` I have made arrangements with Mattdm to host Marketplace AMIs of F27 in the AWS Marketplace. These will be hosted by me as a member of the Fedora community. This allows us to get around certain legal issues that have heretofore prevented the images hosting. * Need Fedora Marketing to assist with writeup for the listing. * TODO F27 submission prior to release date (there is a security audit) Account number for Marketplace deployment is 662243699625. This is legally separate from the FAS managed account. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/339

3 8

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED)