January 2020 - CoreOS - Fedora Mailing-Lists

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/

3 years, 9 months

5
8
0 / 0

Starting kubelet service in FCOS fails

by Thomas Schneider

Hi, I have successfully installed FCOS in KVM from ISO. For installation of K8S I run this command sudo rpm-ostree install kubelet kubeadm kubectl There were no issues during installation. [core@vm192-fcos ~]$ sudo rpm-ostree install kubelet kubeadm kubectl Checking out tree f480038... done Enabled rpm-md repositories: updates fedora kubernetes rpm-md repo 'updates' (cached); generated: 2020-01-21T01:02:46Z rpm-md repo 'fedora' (cached); generated: 2019-10-23T22:52:47Z Updating metadata for 'kubernetes'... done rpm-md repo 'kubernetes'; generated: (invalid timestamp) Importing rpm-md... done Resolving dependencies... done Will download: 10 packages (46.3MB) Downloading from 'fedora'... done Downloading from 'kubernetes'... done Downloading from 'updates'... done Importing packages... done Checking out packages... done Running pre scripts... done Running post scripts... done Running posttrans scripts... done Writing rpmdb... done Writing OSTree commit... done Staging deployment... done Added: conntrack-tools-1.4.5-4.fc31.x86_64 cri-tools-1.13.0-0.x86_64 ebtables-legacy-2.0.10-37.fc31.x86_64 ethtool-2:5.4-1.fc31.x86_64 kubeadm-1.17.2-0.x86_64 kubectl-1.17.2-0.x86_64 kubelet-1.17.2-0.x86_64 libnetfilter_cthelper-1.0.0-16.fc31.x86_64 libnetfilter_cttimeout-1.0.0-14.fc31.x86_64 libnetfilter_queue-1.0.2-14.fc31.x86_64 Run "systemctl reboot" to start a reboot After reboot I tried to start service /kubelet/, but the status shows that the service fails to run: [core@vm192-fcos ~]$ sudo systemctl status kubelet * kubelet.service - kubelet: The Kubernetes Node Agent Loaded: loaded (/usr/lib/systemd/system/kubelet.service; enabled; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/kubelet.service.d `-10-kubeadm.conf Active: activating (auto-restart) (Result: exit-code) since Wed 2020-01-22 08:03:05 UTC; 1s ago Docs: https://kubernetes.io/docs/ Process: 2592 ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS (code=exited, status=255/EXCEPTION) Main PID: 2592 (code=exited, status=255/EXCEPTION) Can you please advise why the service is not starting? Is the procedure for installation of K8S incorrect? THX

3 years, 10 months

3
2
0 / 0

Starting kubelet service in FCOS fails with error: open /var/lib/kubelet/config.yaml: no such file or directory

by Thomas Schneider

Update: I have identified additional information relevant for this error: [core@vm191-fcos ~]$ sudo systemctl status kubelet * kubelet.service - kubelet: The Kubernetes Node Agent Loaded: loaded (/usr/lib/systemd/system/kubelet.service; enabled; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/kubelet.service.d `-10-kubeadm.conf Active: activating (auto-restart) (Result: exit-code) since Tue 2020-01-28 08:17:31 UTC; 9s ago Docs: https://kubernetes.io/docs/ Process: 284824 ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS (code=exited, status=255/EXCEPTION) Main PID: 284824 (code=exited, status=255/EXCEPTION) Jan 28 08:17:41 vm191-fcos systemd[1]: kubelet.service: Scheduled restart job, restart counter is at 7470. Jan 28 08:17:41 vm191-fcos systemd[1]: Stopped kubelet: The Kubernetes Node Agent. Jan 28 08:17:41 vm191-fcos systemd[1]: Started kubelet: The Kubernetes Node Agent. Jan 28 08:17:41 vm191-fcos kubelet[284841]: Flag --cgroup-driver has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information. Jan 28 08:17:42 vm191-fcos kubelet[284841]: F0128 08:17:41.999896 284841 server.go:198] failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "/var/lib/kubelet/config.yaml", error: open /var/lib/kubelet/config.yaml: no such file or directory Jan 28 08:17:42 vm191-fcos systemd[1]: kubelet.service: Main process exited, code=exited, status=255/EXCEPTION Jan 28 08:17:42 vm191-fcos systemd[1]: kubelet.service: Failed with result 'exit-code'. The root cause is clear: /var/lib/kubelet/config.yaml is missing. This raises the question how K8S should be installed on Fedora CoreOS? Should I install the packages in "toolbox" using command sudo dnf install -y kubelet kubeadm kubectl --disableexcludes=kubernetes or should I install a layered package using command sudo rpm-ostree install kubelet kubeadm kubectl Please advise. THX Thomas ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Hi, I have successfully installed FCOS in KVM from ISO. For installation of K8S I run this command sudo rpm-ostree install kubelet kubeadm kubectl There were no issues during installation. [core@vm192-fcos ~]$ sudo rpm-ostree install kubelet kubeadm kubectl Checking out tree f480038... done Enabled rpm-md repositories: updates fedora kubernetes rpm-md repo 'updates' (cached); generated: 2020-01-21T01:02:46Z rpm-md repo 'fedora' (cached); generated: 2019-10-23T22:52:47Z Updating metadata for 'kubernetes'... done rpm-md repo 'kubernetes'; generated: (invalid timestamp) Importing rpm-md... done Resolving dependencies... done Will download: 10 packages (46.3MB) Downloading from 'fedora'... done Downloading from 'kubernetes'... done Downloading from 'updates'... done Importing packages... done Checking out packages... done Running pre scripts... done Running post scripts... done Running posttrans scripts... done Writing rpmdb... done Writing OSTree commit... done Staging deployment... done Added: conntrack-tools-1.4.5-4.fc31.x86_64 cri-tools-1.13.0-0.x86_64 ebtables-legacy-2.0.10-37.fc31.x86_64 ethtool-2:5.4-1.fc31.x86_64 kubeadm-1.17.2-0.x86_64 kubectl-1.17.2-0.x86_64 kubelet-1.17.2-0.x86_64 libnetfilter_cthelper-1.0.0-16.fc31.x86_64 libnetfilter_cttimeout-1.0.0-14.fc31.x86_64 libnetfilter_queue-1.0.2-14.fc31.x86_64 Run "systemctl reboot" to start a reboot After reboot I tried to start service /kubelet/, but the status shows that the service fails to run: [core@vm192-fcos ~]$ sudo systemctl status kubelet * kubelet.service - kubelet: The Kubernetes Node Agent Loaded: loaded (/usr/lib/systemd/system/kubelet.service; enabled; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/kubelet.service.d `-10-kubeadm.conf Active: activating (auto-restart) (Result: exit-code) since Wed 2020-01-22 08:03:05 UTC; 1s ago Docs: https://kubernetes.io/docs/ Process: 2592 ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS (code=exited, status=255/EXCEPTION) Main PID: 2592 (code=exited, status=255/EXCEPTION) Can you please advise why the service is not starting? Is the procedure for installation of K8S incorrect? THX

3 years, 10 months

2
1
0 / 0

Fedora CoreOS Meeting Minutes 2020-01-29

by Dusty Mabe

Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-01-29/fedora_core... Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2020-01-29/fedora_core... Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-01-29/fedora_core... ======================================== #fedora-meeting-1: fedora_coreos_meeting ======================================== Meeting started by dustymabe at 16:30:23 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2020-01-29/fedora_core... . Meeting summary --------------- * roll call (dustymabe, 16:30:35) * Action items from last meeting (dustymabe, 16:33:36) * ACTION: dustymabe to work with x3mboy on FCOS infographic (dustymabe, 16:34:46) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/356 (miabbott, 16:35:31) * slowrie did some initial testing in Azure; ran into DNS problems https://github.com/coreos/fedora-coreos-tracker/issues/356 (dustymabe, 16:36:04) * devconf.cz fedora coreos lab (dustymabe, 16:38:09) * LINK: https://dustymabe.com/2020/01/23/devconf.cz-2020-fedora-coreos-lab/ (dustymabe, 16:38:26) * FCOS "out of preview" retrospective (dustymabe, 16:41:47) * open floor (dustymabe, 16:52:22) * we are in the process of doing a new release for the testing and stable streams (thanks kaeso[m]) (dustymabe, 16:53:18) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/355 (kaeso[m], 16:53:39) * we now have some basic upgrade testing: https://github.com/coreos/fedora-coreos-pipeline/pull/190 (jlebon, 16:54:07) * there is interest from Exoscale (EU cloud provider) to make FCOS available in their cloud (miabbott, 16:55:00) Meeting ended at 17:09:23 UTC. Action Items ------------ * dustymabe to work with x3mboy on FCOS infographic Action Items, by person ----------------------- * dustymabe * dustymabe to work with x3mboy on FCOS infographic * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * dustymabe (56) * zodbot (16) * kaeso[m] (13) * jlebon (12) * red_beard (9) * miabbott (6) * ksinny (5) * bgilbert (3) * abai (1) * mnguyen_ (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

3 years, 10 months

1
0
0 / 0

How to install software packages in FCOS

by Thomas Schneider

Hi, I have successfully installed FCOS in KVM from ISO. Now I need to install some tools, e.g. ncdu, nano, qemu-guest-agent, ... Can you confirm that the recommended way is to run sudo rpm-ostree install <package> If not, please advise how to install software packages in FCOS. THX

3 years, 10 months

4
4
0 / 0

[Fedocal] Reminder meeting : Fedora CoreOS Group Weekly Meeting

by dusty＠dustymabe.com

Dear all, You are kindly invited to the meeting: Fedora CoreOS Group Weekly Meeting on 2020-01-29 from 16:30:00 to 17:30:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: This is the meeting for the Fedora CoreOS Working Group. We typically go over previous meeting action items and then cover all tickets with the meeting keyword: https://github.com/coreos/fedora-coreos-tracker/labels/meeting. For how to run the meeting, see https://github.com/coreos/fedora-coreos-tracker#steps-to-run-the-meeting Source: https://apps.fedoraproject.org/calendar/meeting/9437/

3 years, 10 months

1
0
0 / 0

Updates repo problem?

by Philip Rhoades

People. I am getting: $ sudo rpm-ostree install mc Checking out tree c701882... done Enabled rpm-md repositories: updates fedora Updating metadata for 'updates'... done error: cannot update repo 'updates': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f30&arch... [Could not resolve host: mirrors.fedoraproject.org]; Last error: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f30&arch... [Could not resolve host: mirrors.fedoraproject.org] Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: phil(a)pricom.com.au

3 years, 10 months

2
8
0 / 0

Launching QEMU / KVM with ignition file each time?

by Thomas Schneider

Hi, in the Getting Started guide <https://docs.fedoraproject.org/en-US/fedora-coreos/getting-started/> "Launching with QEMU" it is recommended to "Specify the Ignition file to the hypervisor. In the case of QEMU, this is done with the -fw_cfg parameter, which sets the opt/com.coreos/config key". Question: Is it recommended to startup VMs every time with this -fw_cfg parameter? Is this true for ISO installations on KVM, too? Or must this -fw_cfg parameter only be used for initial startup? Regards Thomas

3 years, 10 months

2
2
0 / 0

Setting up 2nd NIC in FCOS

by Thomas Schneider

Hi, I have successfully installed FCOS in KVM from ISO. Now I added another NIC to the VM, and after rebooting DHCP assigns an IP to this new NIC: [core@vm191-fcos ~]$ nmcli device DEVICE TYPE STATE CONNECTION eth0 ethernet verbunden Wired connection 1 eth1 ethernet verbunden Wired connection 2 lo loopback nicht verwaltet -- [core@vm191-fcos ~]$ nmcli device show eth1 GENERAL.DEVICE: eth1 GENERAL.TYPE: ethernet GENERAL.HWADDR: BE:05:3F:16:2C:CD GENERAL.MTU: 1500 GENERAL.STATE: 100 (verbunden) GENERAL.CONNECTION: Wired connection 2 GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/2 WIRED-PROPERTIES.CARRIER: an IP4.ADDRESS[1]: 192.168.100.102/24 IP4.GATEWAY: 192.168.100.11 IP4.ROUTE[1]: dst = 0.0.0.0/0, nh = 192.168.100.11, mt = 101 IP4.ROUTE[2]: dst = 192.168.100.0/24, nh = 0.0.0.0, mt = 101 IP4.DNS[1]: 10.17.200.80 IP4.DNS[2]: 10.17.122.10 IP4.DOMAIN[1]: IP6.ADDRESS[1]: fe80::50f7:c9cd:ec1e:e75/64 IP6.GATEWAY: -- IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 101 IP6.ROUTE[2]: dst = ff00::/8, nh = ::, mt = 256, table=255 However I don't want NetworkManager to control this NIC eth1. This should be a static IP. Can you please advise how to disable NetworkManager to control this NIC? THX

3 years, 10 months

3
6
0 / 0

Fedora CoreOS Meeting Minutes 2020-01-22

by Benjamin Gilbert

Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-01-22/fedora_core... Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2020-01-22/fedora_core... Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-01-22/fedora_core... ======================================== #fedora-meeting-1: fedora_coreos_meeting ======================================== Meeting started by bgilbert at 16:30:43 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2020-01-22/fedora_core... . Meeting summary --------------- * roll call (bgilbert, 16:30:45) * Action items from last meeting (bgilbert, 16:34:55) * bgilbert has not yet followed up about FCOS infographic (bgilbert, 16:35:26) * ACTION: bgilbert to work with x3mboy on FCOS infographic (bgilbert, 16:35:33) * Open Floor (bgilbert, 16:35:58) * Fedora CoreOS is officially out of preview! (bgilbert, 16:36:20) * LINK: https://fedoramagazine.org/fedora-coreos-out-of-preview/ (bgilbert, 16:36:30) * ACTION: slowrie to help us get the azure image upload/boot tested (bgilbert, 16:37:32) Meeting ended at 16:46:15 UTC. Action Items ------------ * bgilbert to work with x3mboy on FCOS infographic * slowrie to help us get the azure image upload/boot tested Action Items, by person ----------------------- * bgilbert * bgilbert to work with x3mboy on FCOS infographic * slowrie * slowrie to help us get the azure image upload/boot tested * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * bgilbert (27) * zodbot (11) * jdoss (8) * miabbott (4) * slowrie (2) * red_beard (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

3 years, 10 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

CoreOS January 2020