[atomic-wg] Issue #493: Kernel module support
by Joe Doss
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-N...
[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
4 years, 8 months
[atomic-wg] Issue #339: Adding Fedora to AWS Marketplace
by David Duncan
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
4 years, 10 months
[atomic-wg] Issue #510: Openshift Origin 3.9 fails with error message
"Console install failed" on F29 Atomic Host nightly
by Sinny Kumari
sinnykumari reported a new issue against the project: `atomic-wg` that you are following:
``
I tried to set-up basic 3 node OpenShift cluster using playbook playbooks/deploy_cluster.yml from openshift-ansible/openshift-ansible-3.9.41-1 on Fedora 29 Atomic Host latest nightly AMIs (Fedora-AtomicHost-28-20180902.0.x86_64).
It fails during task run [openshift_web_console : Verify that the console is running] with error message "Console install failed."
After doing ssh into master node and running`oc get nodes` says:
```
$ oc get nodes
NAME STATUS ROLES AGE VERSION
node1 NotReady master 2h v1.9.1+a0ce1bc657
node2 NotReady compute 2h v1.9.1+a0ce1bc657
node3 NotReady compute 2h v1.9.1+a0ce1bc657
```
Running kubectl on master node gives following failure message:
```
$ kubectl describe node node1
...
Ready False Wed, 05 Sep 2018 12:11:39 +0000 Wed, 05 Sep 2018 10:08:02 +0000 KubeletNotReady Failed to start ContainerManager Delegation not available for unit type
...
```
Following package versions are available on F29 AH nightly:
runc-1.0.0-50.dev.git20aff4f.fc29.x86_64
systemd-239-3.fc29.x86_64
docker-1.13.1-62.git9cb56fd.fc29.x86_64
`Note:` Same set-up works fine with latest F28 Atomic Host
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/510
4 years, 12 months