[atomic-wg] Issue #181 `Vagrant cannot create synced folder`
by Pagure
jorti reported a new issue against the project: `atomic-wg` that you are following:
``
I just launch an unmodified fedora/25-atomic-host box and I get the error that it cannot create the /vagrant synced dir.
```
$ vagrant up
Bringing machine 'default' up with 'libvirt' provider...
==> default: Creating image (snapshot of base box volume).
==> default: Creating domain with the following settings...
==> default: -- Name: mail-server_default
==> default: -- Domain type: kvm
==> default: -- Cpus: 1
==> default: -- Memory: 512M
==> default: -- Management MAC:
==> default: -- Loader:
==> default: -- Base box: fedora/25-atomic-host
==> default: -- Storage pool: default
==> default: -- Image:
/var/lib/libvirt/images/mail-server_default.img (41G)
==> default: -- Volume Cache: default
==> default: -- Kernel:
==> default: -- Initrd:
==> default: -- Graphics Type: vnc
==> default: -- Graphics Port: 5900
==> default: -- Graphics IP: 127.0.0.1
==> default: -- Graphics Password: Not defined
==> default: -- Video Type: cirrus
==> default: -- Video VRAM: 9216
==> default: -- Keymap: en-us
==> default: -- TPM Path:
==> default: -- INPUT: type=mouse, bus=ps2
==> default: -- Command line :
==> default: Creating shared folders metadata...
==> default: Starting domain.
==> default: Waiting for domain to get an IP address...
==> default: Waiting for SSH to become available...
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Configuring and enabling network interfaces...
==> default: Rsyncing folder: /home/juan/Vagrant/mail-server/ => /vagrant
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mkdir -p /vagrant
Stdout from the command:
Stderr from the command:
mkdir: cannot create directory ‘/vagrant’: Operation not permitted
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/181
6 years, 4 months
[atomic-wg] Issue #176 `status of kubernetes on fedora atomic 25`
by Pagure
jasonbrooks reported a new issue against the project: `atomic-wg` that you are following:
``
We removed kubernetes, etcd, flannel, gluster and ceph from the atomic host for Fedora 25: https://pagure.io/fedora-atomic/c/219c9bb26426811a5f32188c59682ad70c3283e...
The idea is that these pkgs can/should be run as docker containers or system containers. I wrote a post about running kube in containers on CentOS Atomic, but things work the same for Fedora Atomic: http://www.projectatomic.io/blog/2016/09/running-kubernetes-in-containers...
However, we don't currently have fedora containers for kubernetes. There's a year-old PR for this: https://github.com/fedora-cloud/Fedora-Dockerfiles/pull/112. I used this PR as the basis for kube containers for CentOS: https://github.com/CentOS/CentOS-Dockerfiles/tree/master/kubernetes.
Another option is using package layering to install the removed rpms if desired: http://www.projectatomic.io/blog/2016/07/hacking-and-extending-atomic-host/. This works, mostly, but the kube-apiserver that comes with kubernetes-master is granted CAP_NET_BIND_SERVICE so it can use port 443, and package layering won't support this: https://github.com/projectatomic/rpm-ostree/issues/462.
Whether we install kubernetes via package layering or containers, another issue is that the kube we have for fedora 25 is very old, 1.2, and current is 1.4.5. There's a kube 1.4.5 in koji for fc26 (http://koji.fedoraproject.org/koji/buildinfo?buildID=816481), and I've asked Jan about making it available for fedora 25. I built it for f25 and el7 in this copr: https://copr.fedorainfracloud.org/coprs/jasonbrooks/kubernetes/.
kubeadm (http://kubernetes.io/docs/getting-started-guides/kubeadm/) is a slick way to run an up-to-date kube cluster, and the kubernetes project offers rpms for kubeadm, but the kubernetes-cni package they provide doesn't work with atomic. I made a patched package in a copr for f25 and el7 (https://copr.fedorainfracloud.org/coprs/jasonbrooks/kube-release/) and wrote about it here: https://jebpages.com/2016/11/01/installing-kubernetes-on-centos-atomic-ho.... The rpm grabs the binaries from the upstream project, if fedora were to provide this package, we'd probably want to build the binaries ourselves. kubeadm runs kubernetes and etcd in containers, and these containers aren't fedora-based, and they come from upstream. They appear to be based on busybox. Also, kubeadm is considered alpha at this point.
We should:
* try to move to a more recent kubernetes version
* get kubernetes containers in place for fedora
* get fedora versions of the flannel and etcd system containers in place
* document how to install kubernetes and how to use package layering on fedora
* look further into kubeadm
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/176
6 years, 9 months
List of F26 features from Atomic Working Group
by Kushal Das
Hi all.
It is time again to create the list of features we (Atomic Working
Group) will be working on for Fedora 26. We want to discuss the
features in this week's IRC meeting. But first everyone should put up
the ideas to this thread. This will help us to create a proper agenda
for Wednesday's meeting.
Kushal
--
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
6 years, 10 months
[atomic-wg] Issue #160 `Ship fedora-motd in F24 atomic image`
by Pagure
rtnpro added a new comment to an issue you are following:
``
@walters
I created an issue[1] to work on migrating from cron to systemd.
Regarding the first run of ``motdgen-cache-updateinfo``, I am not a big fan of it being run from the PAM stack. That's why I have a workaround in place.
## Use cases
### Installing fedora-motd manually
User can run ``/usr/bin/motdgen`` manually post install to cache update details. Hence, in subsequent runs, neither ``atomic`` or ``dnf`` update info will be checked. May be we can run ``/usr/bin/motdgen`` post install. Also, another way is to start ``motdgen.service`` or enable it at boot. So, ``atomic`` and ``dnf`` commands won't be run at all from the PAM stack, because it has already been run, post install or at system boot.
### Enabling fedora-motd in images
We can enable ``motdgen.service`` at system boot. This will execute ``atomic`` and ``dnf`` commands only during first boot and cache the results. This will result in displaying the motd data from the cached update info result.
@walters what do you think? Is this workaround good enough?
[1]: https://github.com/rtnpro/motdgen/issues/8
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/160
6 years, 10 months
Atomic Composes since 11/21
by Dusty Mabe
It looks like all composes but rawhide composes have been failing since 11/21.
Do we know what the problem is here?
Similarly there haven't been any new f25 ostrees since 11/16. I don't know if the two
are related or not (probably). Anybody know what is going on or do I need to start
digging?
Dusty
6 years, 10 months