September 2018 - Atomic Working Group (ARCHIVED)

[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

[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

[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 #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

[atomic-wg] Issue #497: Add VARIANT_ID=container to /etc/os-release
by Colin Walters 09 Nov '18

09 Nov '18

walters reported a new issue against the project: `atomic-wg` that you are following: `` See https://bugzilla.redhat.com/show_bug.cgi?id=1542060 Probably the "clean" fix is a new `fedora-release-container`. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/497

2 4

[atomic-wg] Issue #502: atomic working group talks/sessions for flock 2018
by Dusty Mabe 12 Oct '18

12 Oct '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` [Flock](https://flocktofedora.org) has been announced and will take place Aug 8th-11th in Dresden Germany. The CFP is open and first round of reviews are due by 15th of June, with last round of reviews due by 15th of July. Let's coordinate our talks for Flock! `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/502

5 6

[atomic-wg] Issue #503: Atomic booth at Devconf.in 2018
by Sinny Kumari 12 Oct '18

12 Oct '18

sinnykumari reported a new issue against the project: `atomic-wg` that you are following: `` [Devconf.in 2018](https://devconf.info/in/2018) will be taking place on August 4-5, 2018. In today's [atomic-wg-apac meeting](https://meetbot.fedoraproject.org/fedora-meeting-1/2018-05-29/fedo… we discussed that it is possible to have atomic booth at the conference venue and @suraj353 will be helping us. We will update further progress in this ticket. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/503

2 2

[atomic-wg] Issue #510: Openshift Origin 3.9 fails with error message "Console install failed" on F29 Atomic Host nightly
by Sinny Kumari 09 Oct '18

09 Oct '18

sinnykumari reported a new issue against the project: `atomic-wg` that you are following: `` I tried to set-up basic 3 node OpenShift cluster using playbook playbooks/deploy_cluster.yml from openshift-ansible/openshift-ansible-3.9.41-1 on Fedora 29 Atomic Host latest nightly AMIs (Fedora-AtomicHost-28-20180902.0.x86_64). It fails during task run [openshift_web_console : Verify that the console is running] with error message "Console install failed." After doing ssh into master node and running`oc get nodes` says: ``` $ oc get nodes NAME STATUS ROLES AGE VERSION node1 NotReady master 2h v1.9.1+a0ce1bc657 node2 NotReady compute 2h v1.9.1+a0ce1bc657 node3 NotReady compute 2h v1.9.1+a0ce1bc657 ``` Running kubectl on master node gives following failure message: ``` $ kubectl describe node node1 ... Ready False Wed, 05 Sep 2018 12:11:39 +0000 Wed, 05 Sep 2018 10:08:02 +0000 KubeletNotReady Failed to start ContainerManager Delegation not available for unit type ... ``` Following package versions are available on F29 AH nightly: runc-1.0.0-50.dev.git20aff4f.fc29.x86_64 systemd-239-3.fc29.x86_64 docker-1.13.1-62.git9cb56fd.fc29.x86_64 `Note:` Same set-up works fine with latest F28 Atomic Host `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/510

5 25

[atomic-wg] Issue #465: Fedora 29 Atomic/Cloud Test Day
by Sinny Kumari 03 Oct '18

03 Oct '18

sinnykumari reported a new issue against the project: `atomic-wg` that you are following: `` As discussed in [atomic-wg](https://meetbot.fedoraproject.org/fedora-meeting-1/2018-05-02/fe… meeting today, we would like to have F29 Atomic/Cloud Test Day preferably right after Beta release. By looking at the [F29 schedule](https://fedoraproject.org/wiki/Releases/29/Schedule), Beta release date can be: 2018-09-18: Beta Release (Preferred target) 2018-09-25: Beta Release (Target #1) It will be good to discuss with Fedora QA team first and then see which date after 25th September works well. Corresponding Fedora QA ticket - https://www.pagure.io/fedora-qa/issue/553 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/465

3 7

Fedora 29 Atomic and Cloud Test Day on Monday, 1st October
by Sinny Kumari 01 Oct '18

01 Oct '18

Hi all, We are organizing Atomic and Cloud Test Day on Monday, 1st October. This Test Day is to make sure that Atomic Host and Cloud artifacts are working as expected in Fedora 29. If something is broken, we catch it and fix them as soon as possible to make sure they are all set before Fedora 29 GA. Details about this Test Day are available in wiki page https://fedoraproject.org/wiki/Test_Day:2018-10-01_Cloud-Atomic_Testday . Once you are done with testing, please enter your results at http://testdays.fedorainfracloud.org/events/49 . See you all on Monday! Thanks, Atomic and Cloud Working Group

2 1

[atomic-wg] Issue #511: Entropy blocking bootup regression in latest release
by Jonathan Lebon 26 Sep '18

26 Sep '18

jlebon reported a new issue against the project: `atomic-wg` that you are following: `` Regression of https://pagure.io/atomic-wg/issue/463 in the latest release (28.20180917.0). See https://bugzilla.redhat.com/show_bug.cgi?id=1572944#c51 and onwards. Should be fixed by https://bodhi.fedoraproject.org/updates/FEDORA-2018-f93103ae20. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/511

3 9

Fedora 29 Talking Points
by Alberto Rodriguez Sanchez 15 Sep '18

15 Sep '18

Hello Teams, I'm Alberto from the Marketing team, I'm asking for help to complete the Fedora 29 Talking points[1]. Talking points are key highlights of the new release. There are different types of talking points for different types of people: general desktop users/everyone, developers, and sysadmins. They are meant to provide a short, effective answer to the question "What cool stuff is in the latest release of Fedora?" They are compelling, not necessarily comprehensive. Best Regards. [1] https://fedoraproject.org/wiki/Fedora_29_talking_points -- Alberto Rodriguez Sanchez <bt0dotninja(a)fedoraproject.org>

1 0

[fedora-atomic] PR #128: post: Disable modular repositories
by Dusty Mabe 10 Sep '18

10 Sep '18

dustymabe opened a new pull-request against the project: `fedora-atomic` that you are following: `` post: Disable modular repositories `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/128

2 4

[atomic-wg] Issue #505: RFC: Make /var/srv system_u:object_r:container_share_t:s0 by default
by Colin Walters 05 Sep '18

05 Sep '18

walters reported a new issue against the project: `atomic-wg` that you are following: `` SELinux and containers - a fairly nontrivial difference we carry from other distributions (Ubuntu, CL) etc. that either don't use SELinux or aren't enforcing. See [this blog](https://www.projectatomic.io/blog/2015/06/using-volumes-with-docker-can-cause-problems-with-selinux/) for some discussion about the `:z/:Z` flags. The fact that we require these labels to be set very, very commonly trips up people. And further, I think a big problem with `:z` is that it forces a relabel every time - it's much better to have the labels set up correctly in the first place! Another related issue is that people do e.g. `-v /home/myuser:/home:z` which will completely break the OS which expects `/home/myuser` to be `user_home_dir_t` etc. Hence, my proposal is: For Atomic Host, change `/var/srv` to be `system_u:object_r:container_share_t:s0` by default. It can then be *assumed* as a default interchange point for containers and the host - no labeling required. Positives: We can start documenting this, and other tools (like a pet container one) can just assume this works. Downsides: If we don't do this for classic as well, we'll have introduced a new special distinction between AH and classic - we currently have very few of those. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/505

4 6

Suggestions re Atomic server and GPU Crypto mining
by Philip Rhoades 04 Sep '18

04 Sep '18

People, I have been following Project Atomic for a while with interest and am at the stage where I am ready to bite the bullet and set up an old machine to test out an Atomic Server. I didn't really have a particular use case in mind - it was just going to be a learning exercise - but more recently I have become interested in testing out some GPU CrypoCurrency mining. So what I am interested in doing is setting up the Atomic Server and creating a container specifically for mining and allow it to use a new GPU card that I will put into the computer - I presume there should be no difficulty with that idea? If that exercise went well, I was thinking of adding a second GPU card and a second container which could mine a different CryptoCurrency by having the second GPU allocated to it? Has anyone here done this sort of thing before? Thanks, Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: phil(a)pricom.com.au

2 2

2wk atomic release candidate: 20180902
by Sayan Chowdhury 04 Sep '18

04 Sep '18

We will attempt today to release the 20180902 images. These images contain the following ostree version/commits from the Fedora-28-updates-20180902.0 updates run: Version: 28.20180902.0 Commit(x86_64): 24d4ceb612af5abfa84f275ca9d8aff862e69d47aaeb177c0d64f30865fd7a9f Commit(aarch64): c4deda4174d1a8f92db430c4f9cd39f79976e6e1b220d310a8b4867b7dda4ab3 Commit(ppc64le): 05af7ceb30fd26545a8cd8e3f2af04bf87fa180bb1eb4e07808da09f5b8695fc The Atomic Host VM images are in the directory: https://kojipkgs.fedoraproject.org/compose/updates/Fedora-28-updates-201809… https://kojipkgs.fedoraproject.org/compose/updates/Fedora-28-updates-201809… https://kojipkgs.fedoraproject.org/compose/updates/Fedora-28-updates-201809… The Atomic Host ISO images are in the directory: https://kojipkgs.fedoraproject.org/compose/updates/Fedora-28-updates-201809… https://kojipkgs.fedoraproject.org/compose/updates/Fedora-28-updates-201809… https://kojipkgs.fedoraproject.org/compose/updates/Fedora-28-updates-201809… The AMIs are here: Fedora-AtomicHost-28_Update-20180902.0.x86_64 eu-west-2 ami-03d4fd9910895515a hvm gp2 Fedora-AtomicHost-28_Update-20180902.0.x86_64 ap-northeast-1 ami-0691f56f20405fb9e hvm gp2 Fedora-AtomicHost-28_Update-20180902.0.x86_64 eu-central-1 ami-020f8f021c9fa34f7 hvm gp2 Fedora-AtomicHost-28_Update-20180902.0.x86_64 us-west-1 ami-00bede34086bfb8fd hvm gp2 Fedora-AtomicHost-28_Update-20180902.0.x86_64 us-west-2 ami-00c19e5357006ae4a hvm gp2 Fedora-AtomicHost-28_Update-20180902.0.x86_64 ap-southeast-2 ami-099321cb614097175 hvm gp2 Fedora-AtomicHost-28_Update-20180902.0.x86_64 ca-central-1 ami-009113452a1ac5984 hvm gp2 Fedora-AtomicHost-28_Update-20180902.0.x86_64 ap-southeast-1 ami-0f4708caece61f8c6 hvm gp2 Fedora-AtomicHost-28_Update-20180902.0.x86_64 sa-east-1 ami-026dee8aed98263ec hvm gp2 Fedora-AtomicHost-28_Update-20180902.0.x86_64 ap-northeast-2 ami-036652cde2830b86d hvm gp2 Fedora-AtomicHost-28_Update-20180902.0.x86_64 eu-west-1 ami-0e6112369d250a0f8 hvm gp2 Fedora-AtomicHost-28_Update-20180902.0.x86_64 ap-south-1 ami-06d77203c373d4fd6 hvm gp2 Fedora-AtomicHost-28_Update-20180902.0.x86_64 eu-west-2 ami-08731650859c6d8aa hvm standard Fedora-AtomicHost-28_Update-20180902.0.x86_64 ap-northeast-1 ami-05eec7a5ce629b935 hvm standard Fedora-AtomicHost-28_Update-20180902.0.x86_64 eu-central-1 ami-00d437839b4950fd8 hvm standard Fedora-AtomicHost-28_Update-20180902.0.x86_64 us-west-1 ami-01eceb486595b836f hvm standard Fedora-AtomicHost-28_Update-20180902.0.x86_64 us-west-2 ami-0f1a1d838deafdc4f hvm standard Fedora-AtomicHost-28_Update-20180902.0.x86_64 ap-southeast-2 ami-006bcec77cf12086d hvm standard Fedora-AtomicHost-28_Update-20180902.0.x86_64 ca-central-1 ami-0fe7b35a393dac031 hvm standard Fedora-AtomicHost-28_Update-20180902.0.x86_64 ap-southeast-1 ami-0f78e70763b6e4fbd hvm standard Fedora-AtomicHost-28_Update-20180902.0.x86_64 sa-east-1 ami-03eafe82c5df1fd7f hvm standard Fedora-AtomicHost-28_Update-20180902.0.x86_64 ap-northeast-2 ami-0724ebf3de7fbd1be hvm standard Fedora-AtomicHost-28_Update-20180902.0.x86_64 eu-west-1 ami-00f43db8f362c0759 hvm standard Fedora-AtomicHost-28_Update-20180902.0.x86_64 ap-south-1 ami-013d51c0afee74942 hvm standard Fedora-AtomicHost-28_Update-20180902.0.x86_64 us-east-1 ami-0ca7e231b2064272d hvm gp2 Fedora-AtomicHost-28_Update-20180902.0.x86_64 us-east-1 ami-027facea3309e3993 hvm standard An example of the diff between this and the previous released version (for x86_64) is: ostree diff commit old: c6b1e97b93424c260baa98518277d87f7f4ebf036c09a9a0aeb7097c33c2099c ostree diff commit new: 24d4ceb612af5abfa84f275ca9d8aff862e69d47aaeb177c0d64f30865fd7a9f Upgraded: cockpit-bridge 175-1.fc28 -> 176-1.fc28 cockpit-docker 175-1.fc28 -> 176-1.fc28 cockpit-networkmanager 175-1.fc28 -> 176-1.fc28 cockpit-system 175-1.fc28 -> 176-1.fc28 container-selinux 2:2.69-1.git452b90d.fc28 -> 2:2.71-1.git5721d74.fc28 fedora-gpg-keys 28-3 -> 28-5 fedora-repos 28-3 -> 28-5 glibc 2.27-30.fc28 -> 2.27-32.fc28 glibc-all-langpacks 2.27-30.fc28 -> 2.27-32.fc28 glibc-common 2.27-30.fc28 -> 2.27-32.fc28 glusterfs 4.1.2-2.fc28 -> 4.1.3-1.fc28 glusterfs-client-xlators 4.1.2-2.fc28 -> 4.1.3-1.fc28 glusterfs-fuse 4.1.2-2.fc28 -> 4.1.3-1.fc28 glusterfs-libs 4.1.2-2.fc28 -> 4.1.3-1.fc28 gnutls 3.6.3-3.fc28 -> 3.6.3-4.fc28 iproute 4.16.0-1.fc28 -> 4.17.0-2.fc28 iproute-tc 4.16.0-1.fc28 -> 4.17.0-2.fc28 kernel 4.17.14-202.fc28 -> 4.17.19-200.fc28 kernel-core 4.17.14-202.fc28 -> 4.17.19-200.fc28 kernel-modules 4.17.14-202.fc28 -> 4.17.19-200.fc28 libnghttp2 1.32.0-1.fc28 -> 1.32.1-1.fc28 libssh 0.8.1-3.fc28 -> 0.8.2-1.fc28 libsss_idmap 1.16.3-1.fc28 -> 1.16.3-2.fc28 libsss_nss_idmap 1.16.3-1.fc28 -> 1.16.3-2.fc28 libsss_sudo 1.16.3-1.fc28 -> 1.16.3-2.fc28 libxcrypt 4.1.1-4.fc28 -> 4.1.2-1.fc28 libxkbcommon 0.8.0-5.fc28 -> 0.8.2-1.fc28 linux-firmware 20180525-85.git7518922b.fc28 -> 20180815-86.gitf1b95fe5.fc28 openldap 2.4.46-2.fc28 -> 2.4.46-3.fc28 openssh 7.7p1-6.fc28 -> 7.8p1-1.fc28 openssh-clients 7.7p1-6.fc28 -> 7.8p1-1.fc28 openssh-server 7.7p1-6.fc28 -> 7.8p1-1.fc28 pcre 8.42-2.fc28 -> 8.42-3.fc28 pcre2 10.31-8.fc28 -> 10.31-10.fc28 podman 0.8.2.1-1.gitf38eb4f.fc28 -> 0.8.3-4.git9d09a4d.fc28 python2-setools 4.1.1-8.1.fc28 -> 4.1.1-9.fc28 python3-setools 4.1.1-8.1.fc28 -> 4.1.1-9.fc28 python3-sssdconfig 1.16.3-1.fc28 -> 1.16.3-2.fc28 runc 2:1.0.0-46.dev.gitb4e2ecb.fc28 -> 2:1.0.0-50.dev.git20aff4f.fc28 setools-console 4.1.1-8.1.fc28 -> 4.1.1-9.fc28 sssd-client 1.16.3-1.fc28 -> 1.16.3-2.fc28 vim-minimal 2:8.1.279-1.fc28 -> 2:8.1.328-1.fc28 Removed: buildah-1.3-1.git4888163.fc28.x86_64 containernetworking-cni-0.6.0-4.fc28.x86_64 Added: containernetworking-plugins-0.7.3-1.fc28.x86_64 Happy Testing!

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED) September 2018