September 2018 - Atomic Working Group (ARCHIVED)

[atomic-wg] Issue #511: Entropy blocking bootup regression in latest release

by Jonathan Lebon

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

4 years, 12 months

3
9
0 / 0

Fedora 29 Talking Points

by Alberto Rodriguez Sanchez

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>

5 years

1
0
0 / 0

[fedora-atomic] PR #128: post: Disable modular repositories

by Dusty Mabe

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

5 years

2
4
0 / 0

[atomic-wg] Issue #505: RFC: Make /var/srv system_u:object_r:container_share_t:s0 by default

by Colin Walters

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

5 years

4
6
0 / 0

Suggestions re Atomic server and GPU Crypto mining

by Philip Rhoades

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

5 years

2
2
0 / 0

2wk atomic release candidate: 20180902

by Sayan Chowdhury

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-2018... https://kojipkgs.fedoraproject.org/compose/updates/Fedora-28-updates-2018... https://kojipkgs.fedoraproject.org/compose/updates/Fedora-28-updates-2018... The Atomic Host ISO images are in the directory: https://kojipkgs.fedoraproject.org/compose/updates/Fedora-28-updates-2018... https://kojipkgs.fedoraproject.org/compose/updates/Fedora-28-updates-2018... https://kojipkgs.fedoraproject.org/compose/updates/Fedora-28-updates-2018... 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!

5 years

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED) September 2018