July 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 19 Jan '19

19 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 22 Dec '18

22 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 10 Nov '18

10 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 13 Oct '18

13 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 13 Oct '18

13 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 06 Sep '18

06 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

[fedora-atomic] PR #124: README.md: fix main manifest file
by Jonathan Lebon 01 Aug '18

01 Aug '18

jlebon opened a new pull-request against the project: `fedora-atomic` that you are following: `` README.md: fix main manifest file `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/124

2 1

[atomic-wg] Issue #508: Container build fails with osbs error
by Honza Horak 25 Jul '18

25 Jul '18

hhorak reported a new issue against the project: `atomic-wg` that you are following: `` See: https://koji.fedoraproject.org/koji/taskinfo?taskID=28570560 ``` Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/koji/daemon.py", line 1244, in runTask response = (handler.run(),) File "/usr/lib/python2.7/site-packages/koji/tasks.py", line 307, in run return koji.util.call_with_argcheck(self.handler, self.params, self.opts) File "/usr/lib/python2.7/site-packages/koji/util.py", line 209, in call_with_argcheck return func(*args, **kwargs) File "/usr/lib/koji-builder-plugins/builder_containerbuild.py", line 815, in handler signing_intent=opts.get('signing_intent', None), File "/usr/lib/koji-builder-plugins/builder_containerbuild.py", line 484, in runBuilds results = [self.createContainer(**kwargs)] File "/usr/lib/koji-builder-plugins/builder_containerbuild.py", line 559, in createContainer build_response = create_method(**create_build_args) File "/usr/lib/python2.7/site-packages/osbs/api.py", line 56, in catch_exceptions return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/osbs/api.py", line 717, in create_build return self._do_create_prod_build(**kwargs) File "/usr/lib/python2.7/site-packages/osbs/api.py", line 666, in _do_create_prod_build osbs_api=self File "/usr/lib/python2.7/site-packages/osbs/build/build_request.py", line 125, in set_params self.spec.set_params(**kwargs) File "/usr/lib/python2.7/site-packages/osbs/build/spec.py", line 305, in set_params 'Please only define one of build_from, build_image, build_imagestream') OsbsValidationException: Please only define one of build_from, build_image, build_imagestream ``` `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/508

2 2

2wk atomic release candidate: 20180723
by Sinny Kumari 24 Jul '18

24 Jul '18

We will attempt tomorrow to release the 20180723 images. These images contain the following ostree version/commits from the Fedora-28-updates-20180722.0 updates run: Version: 28.20180722.0 Commit(x86_64): 106a7095fd46741948ba60dbd0586668ae7abe6336671444ec790d7541a88778 Commit(aarch64): e4cb87910b0729293453004293c1aac3d676b8683f4147a6fb3975092b53810f Commit(ppc64le): 8f316b541744eafb126c06128e1af614f6ab5dccd72a8b722db4b0e295194115 The Atomic Host VM images are in the directory: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28-2018072… https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28-2018072… https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28-2018072… The Atomic Host ISO images are in the directory: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28-2018072… https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28-2018072… https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28-2018072… The AMIs are here: Fedora-AtomicHost-28-20180723.0.x86_64 ap-northeast-1 ami-0de9834fbce78c3b6 hvm standard Fedora-AtomicHost-28-20180723.0.x86_64 ap-northeast-2 ami-0d29052dc554001a2 hvm standard Fedora-AtomicHost-28-20180723.0.x86_64 ap-south-1 ami-0550b10251801e086 hvm standard Fedora-AtomicHost-28-20180723.0.x86_64 ap-southeast-1 ami-0044ba2d261f0e97f hvm standard Fedora-AtomicHost-28-20180723.0.x86_64 ap-southeast-2 ami-043b6817edbba70d2 hvm standard Fedora-AtomicHost-28-20180723.0.x86_64 ca-central-1 ami-02123fa6ba9d33b01 hvm standard Fedora-AtomicHost-28-20180723.0.x86_64 eu-central-1 ami-0330dc0c192a4b33d hvm standard Fedora-AtomicHost-28-20180723.0.x86_64 eu-west-1 ami-0d069275a5c0cca06 hvm standard Fedora-AtomicHost-28-20180723.0.x86_64 eu-west-2 ami-03f67da6021b4a59f hvm standard Fedora-AtomicHost-28-20180723.0.x86_64 sa-east-1 ami-011e32c0bebf3590d hvm standard Fedora-AtomicHost-28-20180723.0.x86_64 us-east-1 ami-0dea83388188d3657 hvm standard Fedora-AtomicHost-28-20180723.0.x86_64 us-west-1 ami-03f717007e01ea3cb hvm standard Fedora-AtomicHost-28-20180723.0.x86_64 us-west-2 ami-091656fb4ba958d60 hvm standard Fedora-AtomicHost-28-20180723.0.x86_64 ap-northeast-1 ami-0e0eff9b8a1c9bc93 hvm gp2 Fedora-AtomicHost-28-20180723.0.x86_64 ap-northeast-2 ami-0173cf2099ccd15b6 hvm gp2 Fedora-AtomicHost-28-20180723.0.x86_64 ap-south-1 ami-05be59fa03aa21c0b hvm gp2 Fedora-AtomicHost-28-20180723.0.x86_64 ap-southeast-1 ami-01847d36a9cfee907 hvm gp2 Fedora-AtomicHost-28-20180723.0.x86_64 ap-southeast-2 ami-0a4dd375f50c199f3 hvm gp2 Fedora-AtomicHost-28-20180723.0.x86_64 ca-central-1 ami-0a7fc88ea611b8707 hvm gp2 Fedora-AtomicHost-28-20180723.0.x86_64 eu-central-1 ami-06bdf0e1da5f25254 hvm gp2 Fedora-AtomicHost-28-20180723.0.x86_64 eu-west-1 ami-0759e35c919fa8dcf hvm gp2 Fedora-AtomicHost-28-20180723.0.x86_64 eu-west-2 ami-0321930bf1b9595a7 hvm gp2 Fedora-AtomicHost-28-20180723.0.x86_64 sa-east-1 ami-00ed208a27f3665ff hvm gp2 Fedora-AtomicHost-28-20180723.0.x86_64 us-east-1 ami-01b65c86e0636af10 hvm gp2 Fedora-AtomicHost-28-20180723.0.x86_64 us-west-1 ami-00a94637ece039300 hvm gp2 Fedora-AtomicHost-28-20180723.0.x86_64 us-west-2 ami-01bd66715f5ea6b39 hvm gp2 An example of the diff between this and the previous released version (for x86_64) is: ostree diff commit old: 5736e832b1fd59208465458265136fbe2aa4ba89517d8bdcc91bc84724f40a8e ostree diff commit new: 106a7095fd46741948ba60dbd0586668ae7abe6336671444ec790d7541a88778 Upgraded: acl 2.2.52-20.fc28 -> 2.2.53-1.fc28 attr 2.4.47-23.fc28 -> 2.4.48-3.fc28 audit 2.8.4-1.fc28 -> 2.8.4-2.fc28 audit-libs 2.8.4-1.fc28 -> 2.8.4-2.fc28 bind-export-libs 32:9.11.3-12.fc28 -> 32:9.11.4-1.fc28 ceph-common 1:12.2.5-1.fc28 -> 1:12.2.6-1.fc28 cockpit-bridge 171-1.fc28 -> 172-1.fc28 cockpit-docker 171-1.fc28 -> 172-1.fc28 cockpit-networkmanager 171-1.fc28 -> 172-1.fc28 cockpit-ostree 171-1.fc28 -> 172-1.fc28 cockpit-system 171-1.fc28 -> 172-1.fc28 curl 7.59.0-4.fc28 -> 7.59.0-5.fc28 dhcp-client 12:4.3.6-20.fc28 -> 12:4.3.6-21.fc28 dhcp-common 12:4.3.6-20.fc28 -> 12:4.3.6-21.fc28 dhcp-libs 12:4.3.6-20.fc28 -> 12:4.3.6-21.fc28 docker 2:1.13.1-59.gitaf6b32b.fc28 -> 2:1.13.1-60.git9cb56fd.fc28 docker-common 2:1.13.1-59.gitaf6b32b.fc28 -> 2:1.13.1-60.git9cb56fd.fc28 docker-rhel-push-plugin 2:1.13.1-59.gitaf6b32b.fc28 -> 2:1.13.1-60.git9cb56fd.fc28 dracut 047-8.git20180305.fc28 -> 048-6.git20180718.fc28.1 dracut-config-generic 047-8.git20180305.fc28 -> 048-6.git20180718.fc28.1 dracut-network 047-8.git20180305.fc28 -> 048-6.git20180718.fc28.1 e2fsprogs 1.43.8-2.fc28 -> 1.44.2-0.fc28 e2fsprogs-libs 1.43.8-2.fc28 -> 1.44.2-0.fc28 file 5.33-6.fc28 -> 5.33-7.fc28 file-libs 5.33-6.fc28 -> 5.33-7.fc28 glibc 2.27-19.fc28 -> 2.27-30.fc28 glibc-all-langpacks 2.27-19.fc28 -> 2.27-30.fc28 glibc-common 2.27-19.fc28 -> 2.27-30.fc28 glusterfs 4.1.1-1.fc28 -> 4.1.1-2.fc28 glusterfs-client-xlators 4.1.1-1.fc28 -> 4.1.1-2.fc28 glusterfs-fuse 4.1.1-1.fc28 -> 4.1.1-2.fc28 glusterfs-libs 4.1.1-1.fc28 -> 4.1.1-2.fc28 kernel 4.17.3-200.fc28 -> 4.17.7-200.fc28 kernel-core 4.17.3-200.fc28 -> 4.17.7-200.fc28 kernel-modules 4.17.3-200.fc28 -> 4.17.7-200.fc28 krb5-libs 1.16.1-7.fc28 -> 1.16.1-13.fc28 leveldb 1.20-1.fc28 -> 1.20-2.fc28 libacl 2.2.52-20.fc28 -> 2.2.53-1.fc28 libattr 2.4.47-23.fc28 -> 2.4.48-3.fc28 libblkid 2.32-2.fc28 -> 2.32.1-1.fc28 libcephfs2 1:12.2.5-1.fc28 -> 1:12.2.6-1.fc28 libcom_err 1.43.8-2.fc28 -> 1.44.2-0.fc28 libcurl 7.59.0-4.fc28 -> 7.59.0-5.fc28 libfdisk 2.32-2.fc28 -> 2.32.1-1.fc28 libgcc 8.1.1-1.fc28 -> 8.1.1-5.fc28 libgomp 8.1.1-1.fc28 -> 8.1.1-5.fc28 libmount 2.32-2.fc28 -> 2.32.1-1.fc28 libnfsidmap 1:2.3.2-0.fc28 -> 1:2.3.2-1.rc3.fc28 librados2 1:12.2.5-1.fc28 -> 1:12.2.6-1.fc28 libradosstriper1 1:12.2.5-1.fc28 -> 1:12.2.6-1.fc28 librbd1 1:12.2.5-1.fc28 -> 1:12.2.6-1.fc28 librgw2 1:12.2.5-1.fc28 -> 1:12.2.6-1.fc28 libsmartcols 2.32-2.fc28 -> 2.32.1-1.fc28 libss 1.43.8-2.fc28 -> 1.44.2-0.fc28 libstdc++ 8.1.1-1.fc28 -> 8.1.1-5.fc28 libuuid 2.32-2.fc28 -> 2.32.1-1.fc28 libxcrypt 4.0.1-3.fc28 -> 4.1.0-1.fc28 microcode_ctl 2:2.1-23.fc28 -> 2:2.1-24.fc28 nfs-utils 1:2.3.2-0.fc28 -> 1:2.3.2-1.rc3.fc28 nss 3.37.3-1.1.fc28 -> 3.38.0-1.0.fc28 nss-softokn 3.37.3-1.1.fc28 -> 3.38.0-1.0.fc28 nss-softokn-freebl 3.37.3-1.1.fc28 -> 3.38.0-1.0.fc28 nss-sysinit 3.37.3-1.1.fc28 -> 3.38.0-1.0.fc28 nss-tools 3.37.3-1.1.fc28 -> 3.38.0-1.0.fc28 nss-util 3.37.3-1.0.fc28 -> 3.38.0-1.0.fc28 openldap 2.4.46-1.fc28 -> 2.4.46-2.fc28 pcre 8.42-1.fc28 -> 8.42-2.fc28 pcre2 10.31-5.fc28 -> 10.31-7.fc28 podman 0.6.5-1.git9d97bd6.fc28 -> 0.7.2-2.git4ca4c5f.fc28 polkit 0.114-1.fc28 -> 0.115-1.fc28 polkit-libs 0.114-1.fc28 -> 0.115-1.fc28 python-cephfs 1:12.2.5-1.fc28 -> 1:12.2.6-1.fc28 python-rados 1:12.2.5-1.fc28 -> 1:12.2.6-1.fc28 python-rbd 1:12.2.5-1.fc28 -> 1:12.2.6-1.fc28 python-rgw 1:12.2.5-1.fc28 -> 1:12.2.6-1.fc28 python2-audit 2.8.4-1.fc28 -> 2.8.4-2.fc28 python2-cryptography 2.2.1-1.fc28 -> 2.3-1.fc28 python3 3.6.5-1.fc28 -> 3.6.6-1.fc28 python3-audit 2.8.4-1.fc28 -> 2.8.4-2.fc28 python3-cryptography 2.2.1-1.fc28 -> 2.3-1.fc28 python3-libs 3.6.5-1.fc28 -> 3.6.6-1.fc28 python3-pytoml 0.1.16-1.fc28 -> 0.1.17-1.fc28 systemd 238-8.git0e0aa59.fc28 -> 238-9.git0e0aa59.fc28 systemd-container 238-8.git0e0aa59.fc28 -> 238-9.git0e0aa59.fc28 systemd-libs 238-8.git0e0aa59.fc28 -> 238-9.git0e0aa59.fc28 systemd-pam 238-8.git0e0aa59.fc28 -> 238-9.git0e0aa59.fc28 systemd-udev 238-8.git0e0aa59.fc28 -> 238-9.git0e0aa59.fc28 util-linux 2.32-2.fc28 -> 2.32.1-1.fc28 vim-minimal 2:8.1.119-2.fc28 -> 2:8.1.189-1.fc28 Removed: grubby-8.40-11.fc28.x86_64 Added: libkcapi-1.1.1-6.fc28.x86_64 libkcapi-hmaccalc-1.1.1-6.fc28.x86_64 Some of the notable changes are updated version of cockpit, podman and dracut Happy testing!

1 0

[atomic-wg] Issue #467: Add Checksum URL for latest qcow2 build
by Katrina Ellison Geltman 13 Jul '18

13 Jul '18

katrinaeg reported a new issue against the project: `atomic-wg` that you are following: `` The latest qcow2 Atomic build is available at https://getfedora.org/atomic_qcow2_latest. As far as I know, the corresponding checksum is not available via URL. Adding a checksum URL would make it possible to validate this image. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/467

4 8

Canceling atomic-wg-apac meeting for 10th July and maybe future meetings as well?
by Sinny Kumari 11 Jul '18

11 Jul '18

Hi all, We are canceling today's atomic-wg-apac meeting as no one is available for meeting. Also, I think it will be good to cancel future atomic-wg APAC meetings because number of community members joining the meeting are very few and doesn't look like it's going to increase. It maybe good to give this time to run Fedora CoreOS WG meeting in APAC friendly Time Zone if people are interested. Thoughts? Regards, Sinny

4 4

2wk atomic release candidate: 20180709
by Sinny Kumari 10 Jul '18

10 Jul '18

We will attempt tomorrow to release the 20180709 images. These images contain the following ostree version/commits from the Fedora-28-updates-20180708.0 updates run: Version: 28.20180708.0 Commit(x86_64): 5736e832b1fd59208465458265136fbe2aa4ba89517d8bdcc91bc84724f40a8e Commit(aarch64): 4066f8e2f2f13709d0cf9a562a1f24cd2459bdc9f13e1ea1034a367586f79dac Commit(ppc64le): a197bd8bfb8cf039e8f2cccf7f743cbb92dde30fffa6ccb0729f8ad13e757b17 The Atomic Host VM images are in the directory: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28-2018070… https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28-2018070… https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28-2018070… The Atomic Host ISO images are in the directory: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28-2018070… https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28-2018070… https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28-2018070… The AMIs are here: Fedora-AtomicHost-28-20180709.0.x86_64 ap-northeast-1 ami-0ec81650fdaaa6bfb hvm standard Fedora-AtomicHost-28-20180709.0.x86_64 ap-northeast-2 ami-014c4ab36fdf1995c hvm standard Fedora-AtomicHost-28-20180709.0.x86_64 ap-south-1 ami-044fc0d4b45f9e960 hvm standard Fedora-AtomicHost-28-20180709.0.x86_64 ap-southeast-1 ami-05ef26c50aed26717 hvm standard Fedora-AtomicHost-28-20180709.0.x86_64 ap-southeast-2 ami-0e2b95a0a6ba40bc6 hvm standard Fedora-AtomicHost-28-20180709.0.x86_64 ca-central-1 ami-01f671df31846d027 hvm standard Fedora-AtomicHost-28-20180709.0.x86_64 eu-central-1 ami-0e1e3859fc5f46513 hvm standard Fedora-AtomicHost-28-20180709.0.x86_64 eu-west-1 ami-06f4a05386a0d8316 hvm standard Fedora-AtomicHost-28-20180709.0.x86_64 eu-west-2 ami-0b3b9b4c637c8fd74 hvm standard Fedora-AtomicHost-28-20180709.0.x86_64 sa-east-1 ami-0e1399a91de00d9e8 hvm standard Fedora-AtomicHost-28-20180709.0.x86_64 us-east-1 ami-0aa16c7b4bf06d509 hvm standard Fedora-AtomicHost-28-20180709.0.x86_64 us-west-1 ami-0324ec86130a35c04 hvm standard Fedora-AtomicHost-28-20180709.0.x86_64 us-west-2 ami-0c3257b018a23d7cc hvm standard Fedora-AtomicHost-28-20180709.0.x86_64 ap-northeast-1 ami-022ebce94a63dd133 hvm gp2 Fedora-AtomicHost-28-20180709.0.x86_64 ap-northeast-2 ami-0e8bee83bf980b07a hvm gp2 Fedora-AtomicHost-28-20180709.0.x86_64 ap-south-1 ami-05f5a36e6143525ed hvm gp2 Fedora-AtomicHost-28-20180709.0.x86_64 ap-southeast-1 ami-0950afca1bf025b3d hvm gp2 Fedora-AtomicHost-28-20180709.0.x86_64 ap-southeast-2 ami-0553c1c315162070a hvm gp2 Fedora-AtomicHost-28-20180709.0.x86_64 ca-central-1 ami-0508d8a0bcbf253cf hvm gp2 Fedora-AtomicHost-28-20180709.0.x86_64 eu-central-1 ami-07717b3c49f85fd49 hvm gp2 Fedora-AtomicHost-28-20180709.0.x86_64 eu-west-1 ami-03025bf7ee7e64b79 hvm gp2 Fedora-AtomicHost-28-20180709.0.x86_64 eu-west-2 ami-0919f0c36b688b923 hvm gp2 Fedora-AtomicHost-28-20180709.0.x86_64 sa-east-1 ami-05f36ff127d962986 hvm gp2 Fedora-AtomicHost-28-20180709.0.x86_64 us-east-1 ami-0a77f497d32491f1c hvm gp2 Fedora-AtomicHost-28-20180709.0.x86_64 us-west-1 ami-039b6fff56357c1bc hvm gp2 Fedora-AtomicHost-28-20180709.0.x86_64 us-west-2 ami-08a7db6e4efae2904 hvm gp2 An example of the diff between this and the previous released version (for x86_64) is: ostree diff commit old: fbed0e26736fc189129f80e9547bfd71497377ca49f0cfd421f173667f5ea825 ostree diff commit new: 5736e832b1fd59208465458265136fbe2aa4ba89517d8bdcc91bc84724f40a8e Upgraded: bind-export-libs 32:9.11.3-6.fc28 -> 32:9.11.3-12.fc28 cockpit-bridge 170-1.fc28 -> 171-1.fc28 cockpit-docker 170-1.fc28 -> 171-1.fc28 cockpit-networkmanager 170-1.fc28 -> 171-1.fc28 cockpit-ostree 170-1.fc28 -> 171-1.fc28 cockpit-system 170-1.fc28 -> 171-1.fc28 container-selinux 2:2.63-1.git284f9e7.fc28 -> 2:2.65-1.gitbf5b26b.fc28 criu 3.8.1-1.fc28 -> 3.9-1.fc28 device-mapper 1.02.146-4.fc28 -> 1.02.146-5.fc28 device-mapper-event 1.02.146-4.fc28 -> 1.02.146-5.fc28 device-mapper-event-libs 1.02.146-4.fc28 -> 1.02.146-5.fc28 device-mapper-libs 1.02.146-4.fc28 -> 1.02.146-5.fc28 dnsmasq 2.79-1.fc28 -> 2.79-3.fc28 efibootmgr 15-6.fc28 -> 16-2.fc28 efivar 34-1.fc28 -> 35-1.fc28 efivar-libs 34-1.fc28 -> 35-1.fc28 elfutils-default-yama-scope 0.172-2.fc28 -> 0.173-1.fc28 elfutils-libelf 0.172-2.fc28 -> 0.173-1.fc28 elfutils-libs 0.172-2.fc28 -> 0.173-1.fc28 firewalld 0.5.2-2.fc28 -> 0.5.3-2.fc28 firewalld-filesystem 0.5.2-2.fc28 -> 0.5.3-2.fc28 glusterfs 4.0.2-1.fc28 -> 4.1.1-1.fc28 glusterfs-client-xlators 4.0.2-1.fc28 -> 4.1.1-1.fc28 glusterfs-fuse 4.0.2-1.fc28 -> 4.1.1-1.fc28 glusterfs-libs 4.0.2-1.fc28 -> 4.1.1-1.fc28 grub2-common 1:2.02-34.fc28 -> 1:2.02-38.fc28 grub2-efi-x64 1:2.02-34.fc28 -> 1:2.02-38.fc28 grub2-pc 1:2.02-34.fc28 -> 1:2.02-38.fc28 grub2-pc-modules 1:2.02-34.fc28 -> 1:2.02-38.fc28 grub2-tools 1:2.02-34.fc28 -> 1:2.02-38.fc28 grub2-tools-extra 1:2.02-34.fc28 -> 1:2.02-38.fc28 grub2-tools-minimal 1:2.02-34.fc28 -> 1:2.02-38.fc28 info 6.5-3.fc28 -> 6.5-4.fc28 iproute 4.15.0-1.fc28 -> 4.16.0-1.fc28 iproute-tc 4.15.0-1.fc28 -> 4.16.0-1.fc28 kernel 4.17.2-200.fc28 -> 4.17.3-200.fc28 kernel-core 4.17.2-200.fc28 -> 4.17.3-200.fc28 kernel-modules 4.17.2-200.fc28 -> 4.17.3-200.fc28 libsemanage 2.8-1.fc28 -> 2.8-2.fc28 libsolv 0.6.34-1.fc28 -> 0.6.34-3.fc28 libsss_idmap 1.16.2-1.fc28 -> 1.16.2-4.fc28 libsss_nss_idmap 1.16.2-1.fc28 -> 1.16.2-4.fc28 libsss_sudo 1.16.2-1.fc28 -> 1.16.2-4.fc28 libxcrypt 4.0.1-1.fc28 -> 4.0.1-3.fc28 libzstd 1.3.4-1.fc28 -> 1.3.5-1.fc28 lsof 4.89-8.fc28 -> 4.89-9.fc28 lvm2 2.02.177-4.fc28 -> 2.02.177-5.fc28 lvm2-libs 2.02.177-4.fc28 -> 2.02.177-5.fc28 oci-systemd-hook 1:0.1.16-1.git05bd9a0.fc28 -> 1:0.1.17-1.git87fb61e.fc28 openssh 7.7p1-3.fc28 -> 7.7p1-5.fc28 openssh-clients 7.7p1-3.fc28 -> 7.7p1-5.fc28 openssh-server 7.7p1-3.fc28 -> 7.7p1-5.fc28 ostree 2018.5-1.fc28 -> 2018.6-4.fc28 ostree-grub2 2018.5-1.fc28 -> 2018.6-4.fc28 ostree-libs 2018.5-1.fc28 -> 2018.6-4.fc28 pcre2 10.31-4.fc28 -> 10.31-5.fc28 podman 0.6.3-1.gitcd39b62.fc28 -> 0.6.5-1.git9d97bd6.fc28 python2-libsemanage 2.8-1.fc28 -> 2.8-2.fc28 python3-babel 2.5.1-2.fc28 -> 2.5.3-1.fc28 python3-firewall 0.5.2-2.fc28 -> 0.5.3-2.fc28 python3-libsemanage 2.8-1.fc28 -> 2.8-2.fc28 python3-sssdconfig 1.16.2-1.fc28 -> 1.16.2-4.fc28 rpm-ostree 2018.5-1.fc28 -> 2018.6-2.fc28 rpm-ostree-libs 2018.5-1.fc28 -> 2018.6-2.fc28 shared-mime-info 1.9-3.fc28 -> 1.10-1.fc28 shim-x64 13-4 -> 15-2 sos 3.5.1-1.fc28 -> 3.6-2.fc28 sssd-client 1.16.2-1.fc28 -> 1.16.2-4.fc28 strace 4.22-1.fc28 -> 4.23-1.fc28 sudo 1.8.22-0.2.b1.fc28 -> 1.8.23-1.fc28 vim-minimal 2:8.1.055-1.fc28 -> 2:8.1.119-2.fc28 Some of the notable changes are updated version of kernel, podman, ostree and rpm-ostree. Note: If you are using ansible 2.6.0 or later version to create openshift cluster using openshift-anisble, you may hit issue https://github.com/openshift/openshift-ansible/issues/7596 . Try some of the workaround mentioned in the issue or switch to ansible-2.5.5 or older version. Happy testing!

1 0

[atomic-wg] Issue #483: perl Dockerfile FROM line is invalid (f28 branch)
by Clement Verna 06 Jul '18

06 Jul '18

cverna reported a new issue against the project: `atomic-wg` that you are following: `` The f28 branch Dockerfile must use a f28 base image. Please update the Dockerfile. https://src.fedoraproject.org/container/perl/blob/f28/f/Dockerfile `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/483

2 3

[Fedocal] Reminder meeting : Atomic Working Group Weekly Meeting
by dusty＠dustymabe.com 04 Jul '18

04 Jul '18

Dear all, You are kindly invited to the meeting: Atomic Working Group Weekly Meeting on 2018-07-04 from 16:30:00 to 17:30:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: This is the meeting for the Fedora Atomic Working Group. We typically go over previous meeting action items and then cover all tickets with the meeting keyword: https://pagure.io/atomic-wg/issues?status=Open&tags=meeting More information available at: [https://fedoraproject.org/wiki/Atomic_WG#Meetings](https://fedoraproject.or… Source: https://apps.fedoraproject.org/calendar/meeting/6952/

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED) July 2018