Hi everybody, I am studying the systemd-nspawn containers and I noticed
that there is a bug in SELinux policy that prevents the user to use
# machinectl login foo
# machinectl start foo
# machinectl stop foo
Meanwhile the SELinux maintainers patch such bug, I would like to
manually adjust SELinux policy to allow machinectl and at the same time
to not leave security holes around. Since I am not a SELinux expert, I
would like to ask you for suggestions.
Thank you for your time
Most of the Working Group members are travelling for DevConf, so we are
cancelling our meeting today.
A few of us still chatting on the #fedora-cloud channel.
Fedora Cloud Engineer
CPython Core Developer
I have a F25 64bit server - it is mainly used to run Qmail and EZMLM but
also has a couple of trivial web sites on it. I am thinking of moving
about a dozen small Rails and Jekyll websites off Digital Ocean and back
on to this server. Should I do a clean, bare-metal install of Fedora
Atomic Host onto this server, convert the Qmail + EZMLM services into a
Docker image to run on this new FPA server and then move all my DO web
sites on to this new FPA as Docker images as well?
PO Box 896
Cowra NSW 2794
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2017-01-25 from 17:00:00 to 18:00:00 UTC
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
Note: please don't respond to this email. Please continue discussion
in the linked ticket.
This is a partial implementation of releng ticket 6545  which is a
migration of the old releng trac ticket 6313 .
Gross simplification: In the ticket two things were requested:
- The ostree commits should have slower cadence
- Version numbers of the pungi run match the ostree commits
I have got together with colin (some time ago) and patrick (recently)
to discuss an implementation for the first bulleted ask: "ostree
commits should have slower cadence". This proposal is for that work
Currently what we have is ostree composes that run as part of (or
immediately after) bodhi runs that push out new updated rpms into the
updates or updates-testing yum repos in Fedora. As part of this a new
ostree commit is created with the new content and the
fedora-atomic/25/x86_64/docker-host ref within the ostree repo gets
This fedora-atomic/25/x86_64/docker-host ref is the one that our users
running atomic host are following. It means that when they run
`rpm-ostree upgrade` they are getting the latest commit from the last
bodhi run, not the commit from the last two week release.
We'd like to change this so that user's only get new commits ~every
two weeks (when we do a release). We can achieve this by making a
- change bodhi ostree composes to update a different "ref"
- we are proposing this ref should be called
since it tracks the updates yum repo
- alternatively we already have
which tracks the updates-testing yum repo.
In the future we will change this name to
"updates-testing" vs just "testing"
- updating the two week release process to update the
- This means that ref will only get updated when we do a release.
- building the iso/cloud images from the "updates" ref
but pointing them to the 2wk release ref
- This will mean we can still get new images every night to test
but when we release one of these images it tracks the 2wk ref
I've talked with patrick and these changes are pretty simple to make.
We welcome feedback, but hope to implement these changes soon.
I'll be updating ticket 6545 with this information as well. Please
comment with any discussion in the ticket!
Please test it out so that we can get the new kernel karma'd as soon as possible:
ostree remote add --set=gpg-verify=false kerneltest https://dustymabe.fedorapeople.org/repo/
rpm-ostree rebase kerneltest:fedora-atomic/25/x86_64/docker-host
This tree currently has the following changes from current stable:
kernel 4.9.4-201.fc25 -> 4.9.5-200.fc25
kernel-core 4.9.4-201.fc25 -> 4.9.5-200.fc25
kernel-modules 4.9.4-201.fc25 -> 4.9.5-200.fc25
kubernetes 1.4.7-1.fc25 -> 1.5.2-2.fc25
kubernetes-client 1.4.7-1.fc25 -> 1.5.2-2.fc25
kubernetes-master 1.4.7-1.fc25 -> 1.5.2-2.fc25
kubernetes-node 1.4.7-1.fc25 -> 1.5.2-2.fc25
I'll give a link to the bodhi update when it is submitted.