wifi: New example

[cgwalters]

Support for wireless on FCOS has come up several times, and is
one of the notable differences with current Fedora IoT. It also
highlights a gap in our support for secret management.

[cgwalters]

xref coreos/fedora-coreos-tracker#862

[akostadinov]

Hi, it is not clear to me how to apply this on a bare metal installation media.

[jmarrero]

lgtm

[jmarrero]

Hi, it is not clear to me how to apply this on a bare metal installation media.

Once you have the container built you can rebase your installation using these steps: https://coreos.github.io/rpm-ostree/layering/ feel free to reach out if you have any additional questions.

[akostadinov]

Hi, it is not clear to me how to apply this on a bare metal installation media.

Once you have the container built you can rebase your installation using these steps: https://coreos.github.io/rpm-ostree/layering/ feel free to reach out if you have any additional questions.

I don't get the idea.

What is the point in rebasing to a container image instead of just running rpm-ostree locally? How does it help when re-provisioning the machine for whatever reason with coreos-installer (e.g. when butane is changed)?

[jmarrero]

Hi, it is not clear to me how to apply this on a bare metal installation media.

Once you have the container built you can rebase your installation using these steps: https://coreos.github.io/rpm-ostree/layering/ feel free to reach out if you have any additional questions.

I don't get the idea.

What is the point in rebasing to a container image instead of just running rpm-ostree locally? How does it help when re-provisioning the machine for whatever reason with coreos-installer (e.g. when butane is changed)?

While currently we don't have a mechanism to directly install your generated container on bare-metal that is something that we plan on doing in the future see coreos/fedora-coreos-tracker#1151

The current approach is something that enables an easy way to manage the host OS software at scale. For example If you have hundreds of nodes you need to be based on the exact OS level + packages you can now just rebase all of those hosts on your image using rpm-ostree without worrying if any software is different on them. Also your Dockerfile in git for can help you define packages and config in a way that you can easily track and audit.

[romfreiman]

~/work/coreos-layering-examples/wifi [main]> podman build -f Dockerfile \STEP 1/3: FROM quay.io/coreos-assembler/fcos:testing-devel STEP 2/3: RUN rpm-ostree install NetworkManager-wifi NetworkManager-wwan wpa_supplicant wireless-regdb && rpm-ostree cleanup -m && ostree container commit container exited on segmentation fault Error: error building at STEP "RUN rpm-ostree install NetworkManager-wifi NetworkManager-wwan wpa_supplicant wireless-regdb && rpm-ostree cleanup -m && ostree container commit": error while running runtime: exit status 1

[jmarrero]

@romfreiman
It works on my machine™

I wonder if it's a podman/environment version issue somehow...

I tested by running

podman build  . 

and

podman build -f Dockerfile --no-cache

both build as expected.

My podman version is:

podman version 4.1.0

In any case, if the issue persists for you please include as much information about your environment and open an issue. It's easy (at least for me) to miss comments closed PRs.