Timothée Ravier

Partial fix in https://github.com/coreos/fedora-coreos-docs/pull/349

I would prefer we add a new example and keep this one. As Dusty said, we need this specific example to point people to when then need vim and not...

Example: ``` storage: files: - path: /etc/chrony.conf overwrite: yes mode: 0644 contents: inline: | ... ```

We could maybe enable GitHub pages here and push to a docs branch with a subpath based on PR number.

It's also fairly easy to setup GitHub Pages for a forked repo: https://github.com/coreos/fedora-coreos-tracker/blob/main/docs/testing-project-documentation-changes.md

> I'd rather not fill the production repo with a bunch of test builds. If we want to go the GitHub Pages route, maybe we could create a dedicated repo...

We also have the option of building toolbox inside of a podman container on the FCOS VMs before running the tests on the VM itself. The best scenario for us...

We now have tests in Fedora CoreOS CI but of course that does not covers changes here so this is still relevant. I'll have to take a look at the...

Current plan based on discussion with Zuul/SF maintainers/members: - Add Fedora CoreOS QCOW2 images for all streams (stable, testing, next) to SF nodepool - Write a Butane config to pass...

See also discussion in https://github.com/containers/podman/issues/10296