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

[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

[atomic-wg] Issue #509: change in url for download location after we started using updates composes
by Dusty Mabe 30 Aug '18

30 Aug '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` We recently started releasing media that was created as part of the updates composes. A side effect of this is that the directory the media gets copied into has changed it's naming structure.. for example our last release was: ``` https://dl.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-2018080… ``` where our current release is: ``` https://dl.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-201808… ``` This was an undesired change. We need to figure out if we want to keep it this way or change it back. My vote would be that we change it back for the next release. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/509

2 8

Review Fedora 29 deliverables
by Ben Cotton 28 Aug '18

28 Aug '18

Please review the list of release-blocking deliverables for Atomic Host[1]. Let me know if any images are missing or if the blocking status or target size have changed since the last release. [1] https://fedoraproject.org/wiki/Releases/29/ReleaseBlocking#Atomic_Host Thanks, BC -- Ben Cotton Fedora Program Manager TZ=America/Indiana/Indianapolis

2 1

[fedora-atomic] PR #127: Rawhide being F30
by Mohan Boddu 14 Aug '18

14 Aug '18

mohanboddu opened a new pull-request against the project: `fedora-atomic` that you are following: `` Rawhide being F30 `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/127

3 2

[fedora-atomic] PR #126: Branching F29 from rawhide
by Mohan Boddu 14 Aug '18

14 Aug '18

mohanboddu opened a new pull-request against the project: `fedora-atomic` that you are following: `` Branching F29 from rawhide `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/126

2 2

[fedora-atomic] PR #125: Port manifest file to YAML
by Colin Walters 11 Aug '18

11 Aug '18

walters opened a new pull-request against the project: `fedora-atomic` that you are following: `` Port manifest file to YAML `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/125

2 3

[atomic-wg] Issue #283: please include documentation for run label inside Fedora container guidelines
by Tomas Tomecek 10 Aug '18

10 Aug '18

The status of the issue: `please include documentation for run label inside Fedora container guidelines` of project: `atomic-wg` has been updated to: Closed as Duplicate by ttomecek. https://pagure.io/atomic-wg/issue/283

1 0

[atomic-wg] Issue #283: please include documentation for run label inside Fedora container guidelines
by Tomas Tomecek 10 Aug '18

10 Aug '18

ttomecek added a new comment to an issue you are following: `` dupe of #244 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/283

1 0

[atomic-wg] Issue #276: Set architecture label in the base container image
by Clement Verna 10 Aug '18

10 Aug '18

The status of the issue: `Set architecture label in the base container image` of project: `atomic-wg` has been updated to: Closed as Fixed by cverna. https://pagure.io/atomic-wg/issue/276

1 0

2wk atomic release candidate: 20180806
by Sinny Kumari 06 Aug '18

06 Aug '18

We will attempt tomorrow to release the 20180806 images. These images contain the following ostree version/commits from the Fedora-28-updates-20180804.0 updates run: Version: 28.20180804.0 Commit(x86_64): 5633f5b369b166d104720a4da31da1ac6b5e3c0de5c5bae70cb40a850ded e502 Commit(aarch64): 99267073f82f4d7161bb36c5229d4d cf0518503ea8eda161483278053a68df10 Commit(ppc64le): 6b4f16f98c5609629bb1bac2f64e69 c930d9e42a7bd13aca2fcae0d928c0a666 The Atomic Host VM images are in the directory: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28- 20180806.0/compose/AtomicHost/x86_64/images/ https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28- 20180806.0/compose/AtomicHost/aarch64/images/ https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28- 20180806.0/compose/AtomicHost/ppc64le/images/ The Atomic Host ISO images are in the directory: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28- 20180806.0/compose/AtomicHost/x86_64/iso/ https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28- 20180806.0/compose/AtomicHost/aarch64/iso/ https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28- 20180806.0/compose/AtomicHost/ppc64le/iso/ The AMIs are here: Fedora-AtomicHost-28-20180806.0.x86_64 ap-northeast-1 ami-09639dbbc8353285c hvm standard Fedora-AtomicHost-28-20180806.0.x86_64 ap-northeast-2 ami-035a3d79940cce1f9 hvm standard Fedora-AtomicHost-28-20180806.0.x86_64 ap-south-1 ami-0779345f8b1265e92 hvm standard Fedora-AtomicHost-28-20180806.0.x86_64 ap-southeast-1 ami-0c69be1633d71b04d hvm standard Fedora-AtomicHost-28-20180806.0.x86_64 ap-southeast-2 ami-014202180432121f9 hvm standard Fedora-AtomicHost-28-20180806.0.x86_64 ca-central-1 ami-0e85cacb9f8136768 hvm standard Fedora-AtomicHost-28-20180806.0.x86_64 eu-central-1 ami-0113d4e89d8c67707 hvm standard Fedora-AtomicHost-28-20180806.0.x86_64 eu-west-1 ami-046c0df3013912e4f hvm standard Fedora-AtomicHost-28-20180806.0.x86_64 eu-west-2 ami-098962da8bf012633 hvm standard Fedora-AtomicHost-28-20180806.0.x86_64 sa-east-1 ami-04d49baefa2ac2db2 hvm standard Fedora-AtomicHost-28-20180806.0.x86_64 us-east-1 ami-0f8cf703c4fe5a7b7 hvm standard Fedora-AtomicHost-28-20180806.0.x86_64 us-west-1 ami-0a6c7c39f9060f49b hvm standard Fedora-AtomicHost-28-20180806.0.x86_64 us-west-2 ami-041a944911effee40 hvm standard Fedora-AtomicHost-28-20180806.0.x86_64 ap-northeast-1 ami-0be6a06c67b7a2428 hvm gp2 Fedora-AtomicHost-28-20180806.0.x86_64 ap-northeast-2 ami-0401b39b6362e5738 hvm gp2 Fedora-AtomicHost-28-20180806.0.x86_64 ap-south-1 ami-0cbb364583cc74a0f hvm gp2 Fedora-AtomicHost-28-20180806.0.x86_64 ap-southeast-1 ami-01f3164561a69bec5 hvm gp2 Fedora-AtomicHost-28-20180806.0.x86_64 ap-southeast-2 ami-0a5b4918b8f5d9480 hvm gp2 Fedora-AtomicHost-28-20180806.0.x86_64 ca-central-1 ami-09cf8fc16cbbe7b66 hvm gp2 Fedora-AtomicHost-28-20180806.0.x86_64 eu-central-1 ami-0ec6f096250fd12f7 hvm gp2 Fedora-AtomicHost-28-20180806.0.x86_64 eu-west-1 ami-002823636d0bcbb91 hvm gp2 Fedora-AtomicHost-28-20180806.0.x86_64 eu-west-2 ami-0883d4366444c701e hvm gp2 Fedora-AtomicHost-28-20180806.0.x86_64 sa-east-1 ami-0de81360cecc1d8a5 hvm gp2 Fedora-AtomicHost-28-20180806.0.x86_64 us-east-1 ami-0acb3fb9eb2c4d4d2 hvm gp2 Fedora-AtomicHost-28-20180806.0.x86_64 us-west-1 ami-076e9a26a00400de0 hvm gp2 Fedora-AtomicHost-28-20180806.0.x86_64 us-west-2 ami-0779e12563f8eea88 hvm gp2 An example of the diff between this and the previous released version (for x86_64) is: ostree diff commit old: 106a7095fd46741948ba60dbd05866 68ae7abe6336671444ec790d7541a88778 ostree diff commit new: 5633f5b369b166d104720a4da31da1 ac6b5e3c0de5c5bae70cb40a850dede502 Upgraded: bubblewrap 0.2.1-1.fc28 -> 0.3.0-2.fc28 ceph-common 1:12.2.6-1.fc28 -> 1:12.2.7-1.fc28 cockpit-bridge 172-1.fc28 -> 174-1.fc28 cockpit-docker 172-1.fc28 -> 174-1.fc28 cockpit-networkmanager 172-1.fc28 -> 174-1.fc28 cockpit-ostree 172-1.fc28 -> 174-1.fc28 cockpit-system 172-1.fc28 -> 174-1.fc28 container-selinux 2:2.65-1.gitbf5b26b.fc28 -> 2:2.69-1.git452b90d.fc28 criu 3.9-1.fc28 -> 3.10-4.fc28 dnsmasq 2.79-3.fc28 -> 2.79-5.fc28 dracut 048-6.git20180718.fc28.1 -> 048-14.git20180726.fc28 dracut-config-generic 048-6.git20180718.fc28.1 -> 048-14.git20180726.fc28 dracut-network 048-6.git20180718.fc28.1 -> 048-14.git20180726.fc28 glusterfs 4.1.1-2.fc28 -> 4.1.2-2.fc28 glusterfs-client-xlators 4.1.1-2.fc28 -> 4.1.2-2.fc28 glusterfs-fuse 4.1.1-2.fc28 -> 4.1.2-2.fc28 glusterfs-libs 4.1.1-2.fc28 -> 4.1.2-2.fc28 gnutls 3.6.2-3.fc28 -> 3.6.3-2.fc28 kernel 4.17.7-200.fc28 -> 4.17.11-200.fc28 kernel-core 4.17.7-200.fc28 -> 4.17.11-200.fc28 kernel-modules 4.17.7-200.fc28 -> 4.17.11-200.fc28 kpartx 0.7.4-2.git07e7bd5.fc28 -> 0.7.4-3.git07e7bd5.fc28 libcephfs2 1:12.2.6-1.fc28 -> 1:12.2.7-1.fc28 libkcapi 1.1.1-6.fc28 -> 1.1.1-11.fc28 libkcapi-hmaccalc 1.1.1-6.fc28 -> 1.1.1-11.fc28 libpng 2:1.6.34-3.fc28 -> 2:1.6.34-6.fc28 librados2 1:12.2.6-1.fc28 -> 1:12.2.7-1.fc28 libradosstriper1 1:12.2.6-1.fc28 -> 1:12.2.7-1.fc28 librbd1 1:12.2.6-1.fc28 -> 1:12.2.7-1.fc28 librgw2 1:12.2.6-1.fc28 -> 1:12.2.7-1.fc28 libtirpc 1.0.3-1.rc1.fc28 -> 1.0.3-3.rc2.fc28 libxcrypt 4.1.0-1.fc28 -> 4.1.1-1.fc28 libxkbcommon 0.8.0-2.fc28 -> 0.8.0-5.fc28 mozjs52 52.8.0-1.fc28 -> 52.9.0-1.fc28 oci-systemd-hook 1:0.1.17-1.git87fb61e.fc28 -> 1:0.1.17-3.gitbd86a79.fc28 ostree 2018.6-4.fc28 -> 2018.7-1.fc28 ostree-grub2 2018.6-4.fc28 -> 2018.7-1.fc28 ostree-libs 2018.6-4.fc28 -> 2018.7-1.fc28 podman 0.7.2-2.git4ca4c5f.fc28 -> 0.7.4-4.git80612fb.fc28 python-cephfs 1:12.2.6-1.fc28 -> 1:12.2.7-1.fc28 python-rados 1:12.2.6-1.fc28 -> 1:12.2.7-1.fc28 python-rbd 1:12.2.6-1.fc28 -> 1:12.2.7-1.fc28 python-rgw 1:12.2.6-1.fc28 -> 1:12.2.7-1.fc28 python2-setools 4.1.1-6.fc28 -> 4.1.1-8.1.fc28 python2-setuptools 39.2.0-1.fc28 -> 39.2.0-6.fc28 python3-setools 4.1.1-6.fc28 -> 4.1.1-8.1.fc28 python3-setuptools 39.2.0-1.fc28 -> 39.2.0-6.fc28 selinux-policy 3.14.1-32.fc28 -> 3.14.1-37.fc28 selinux-policy-targeted 3.14.1-32.fc28 -> 3.14.1-37.fc28 setools-console 4.1.1-6.fc28 -> 4.1.1-8.1.fc28 vim-minimal 2:8.1.189-1.fc28 -> 2:8.1.233-1.fc28 Some of the notable changes are updated version of cockpit, ostree and podman. Happy testing!

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED) August 2018