Install FCOS on a bare metal server
by arnaud gaboury
I run a cloud bare metal server with Fedora Silverblue. The server is
far from being full of services and settings, so I would like to take
the opportunity to migrate to FCOS before too many apps are deployed.
Following Fedoraproject documentation[0], I have been able to write a
simple ignition file with no issues. But then I have no idea how to
proceed to install FCOS, as I can't boot the server from an ISO file.
My first though is to install coreos-installer, via a package or a
docker image, then run coreos-installer as described in the coreos
github[1] with my .ign file, then reboot. Will I be able to thereafter
ssh the server as core user with the given ssh key? Or shall I write
sshd settings in my ignition file to allow ssh from key for user core?
Is it the correct process? Or is the process something more complicated
involving PXE?
I have read the excellent paper, as usual, written by Dusty[2], but the
process is dedicated to a VM. Maybe can I make some changes to adapt the
method?
Thank you for any hint to a clear way to install coreOS from Silverblue.
I may then write a How-To as it seems clear directions are missing.
[0]https://docs.fedoraproject.org/en-US/fedora-coreos/bare-metal/
[1]https://github.com/coreos/coreos-installer
[2]https://dustymabe.com/2020/01/23/devconf.cz-2020-fedora-coreos-lab/
4 years, 2 months
Customize RPM-OSTree
by Oliver Rainer
Hi, I was following the advices of https://www.projectatomic.io/blog/2017/12/compose-custom-ostree/ to build a custom OSTree. I am not able to do same steps for Fedora CoreOS (stable stream) because i do not know where to get the package configuration (like fedora-atomic-host-base.json) files.
My question is the following...
Am I leaving now the intended way of updating CoreOS or is there a way to build custom update ostrees?
The background is that our baremetal device most probably will be offline resp. has no public internet access at customer sites (not fully offline, but only accessible through company network)
Thanks for any advice
4 years, 2 months
Fedora CoreOS Meeting Minutes 2020-02-05
by Dusty Mabe
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-02-05/fedora_core...
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2020-02-05/fedora_core...
Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-02-05/fedora_core...
========================================
#fedora-meeting-1: fedora_coreos_meeting
========================================
Meeting started by dustymabe at 16:30:39 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-02-05/fedora_core...
.
Meeting summary
---------------
* roll call (dustymabe, 16:30:43)
* Action items from last meeting (dustymabe, 16:35:04)
* ACTION: dustymabe to work with x3mboy on FCOS infographic
(dustymabe, 16:35:35)
* next stream (dustymabe, 16:35:51)
* ACTION: dustymabe to open a tracker ticket where we discuss major
changes for the f32 rebase, including fedora proposed changes for
f32 (dustymabe, 16:54:42)
* ACTION: cyberpear to file tracker ticket for FCCT in the initramfs
(bgilbert, 16:56:00)
* ACTION: jlebon to investigate if latest moby-engine upstream has any
cgroups v2 support (dustymabe, 16:57:55)
* ACTION: mnguyen_ will ask moby-engine maintainer(s) about a rebase
to latest upstream release for f32 (dustymabe, 16:59:48)
* Include wireguard-tools package in FCOS (dustymabe, 17:00:23)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/362
(dustymabe, 17:00:34)
* metal installer requires re-fetching metal image (fulliso)
(dustymabe, 17:20:53)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/352
(bgilbert, 17:22:15)
* fcct in initrd ticket
https://github.com/coreos/fedora-coreos-tracker/issues/371
(cyberpear, 17:38:12)
* rust packaging in Fedora (dustymabe, 17:38:23)
* LINK: https://pagure.io/koji/pull-request/1956. (ignatenkobrain,
17:40:52)
* LINK:
https://gist.github.com/ignatenkobrain/f2529a3f9e34848fa63587db94089a0f
(ignatenkobrain, 17:41:27)
* LINK: https://pagure.io/sidetag-koji-plugin/pull-request/9
(ignatenkobrain, 17:44:32)
* ACTION: dustymabe to work with ignatenkobrain and koji devs to try
to drive rust packaging to a better state (dustymabe, 17:53:52)
* to build Rust packages in stable Fedora, build in rawhide and then
ping ignatenkobrain (bgilbert, 17:54:19)
* open floor (dustymabe, 17:54:58)
* we did a testing and stable release that started rollout on monday -
haven't heard of any issues (dustymabe, 17:55:38)
Meeting ended at 17:57:40 UTC.
Action Items
------------
* dustymabe to work with x3mboy on FCOS infographic
* dustymabe to open a tracker ticket where we discuss major changes for
the f32 rebase, including fedora proposed changes for f32
* cyberpear to file tracker ticket for FCCT in the initramfs
* jlebon to investigate if latest moby-engine upstream has any cgroups
v2 support
* mnguyen_ will ask moby-engine maintainer(s) about a rebase to latest
upstream release for f32
* dustymabe to work with ignatenkobrain and koji devs to try to drive
rust packaging to a better state
Action Items, by person
-----------------------
* cyberpear
* cyberpear to file tracker ticket for FCCT in the initramfs
* dustymabe
* dustymabe to work with x3mboy on FCOS infographic
* dustymabe to open a tracker ticket where we discuss major changes
for the f32 rebase, including fedora proposed changes for f32
* dustymabe to work with ignatenkobrain and koji devs to try to drive
rust packaging to a better state
* ignatenkobrain
* dustymabe to work with ignatenkobrain and koji devs to try to drive
rust packaging to a better state
* jlebon
* jlebon to investigate if latest moby-engine upstream has any cgroups
v2 support
* mnguyen_
* mnguyen_ will ask moby-engine maintainer(s) about a rebase to latest
upstream release for f32
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* dustymabe (166)
* bgilbert (47)
* ignatenkobrain (24)
* jlebon (22)
* jdoss (20)
* zodbot (20)
* walters (15)
* kaeso[m] (13)
* cyberpear (11)
* kwizart (2)
* mnguyen_ (2)
* miabbott (1)
* bgilbert__ (1)
* red_beard (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
4 years, 2 months
Replace registries.conf within ignition
by Jorge Rúa
Hi there,
I am trying to do something similar to what Dusty show in Devconf, but
instead of pulling etcd from quay.io using our internal registry and
different image.
What i am doing is adding an storage stanza in ignition file with the
registries.conf content. But for some reason it goes into emergency target.
No need to say the ignition file is validated before.
What would you suggest to modify this file so podman is able to pull an
image from an internal registry?
Thanks for your help
4 years, 2 months
