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
Layering packages with `rpm-ostree install` is generally discouraged. Instead, you should try your best to run software in containers. For example, Fedora CoreOS includes `toolbox` to make it easy to create and enter a container to manage the host from:
https://github.com/coreos/fedora-coreos-tracker/issues/90
This is the same toolbox used in Fedora Silverblue. There's still more work to be done though to get it working well for the sysadmin "privileged" case.
Re. qemu-guest-agent specifically, see the relevant discussions in https://github.com/coreos/fedora-coreos-tracker/issues/74.
On Wed, Jan 22, 2020 at 2:35 AM Thomas Schneider 74cmonty@gmail.com wrote:
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 _______________________________________________ CoreOS mailing list -- coreos@lists.fedoraproject.org To unsubscribe send an email to coreos-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org
Hi,
my understanding of your reply is that any additional software required should run in container(s).
With regards to qemu-guest-agent my understanding is that it was decided not to include it in FCOS. However I can install it if I think it's needed. Btw, qemu-guest-agent works as expected the way I installed it.
My question with regards to the other packages (ncdu, nano, ...) installed: Do you recommend to revert this installation?
And what about K8S? I found many documenation (e.g. here https://github.com/coreos/coreos-kubernetes/blob/master/Documentation/kubernetes-on-baremetal.md) for the installation of K8S on CoreOS. But ultimately they are pointing to using "Tectonic". If I don't want to use "Tectonic" (for whatever reason), are there any other options? Can I use this https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/ K8S getting started guide (from K8S project)?
THX Thomas
Am 22.01.2020 um 17:57 schrieb Jonathan Lebon:
Layering packages with `rpm-ostree install` is generally discouraged. Instead, you should try your best to run software in containers. For example, Fedora CoreOS includes `toolbox` to make it easy to create and enter a container to manage the host from:
https://github.com/coreos/fedora-coreos-tracker/issues/90
This is the same toolbox used in Fedora Silverblue. There's still more work to be done though to get it working well for the sysadmin "privileged" case.
Re. qemu-guest-agent specifically, see the relevant discussions in https://github.com/coreos/fedora-coreos-tracker/issues/74.
On Wed, Jan 22, 2020 at 2:35 AM Thomas Schneider 74cmonty@gmail.com wrote:
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 _______________________________________________ CoreOS mailing list -- coreos@lists.fedoraproject.org To unsubscribe send an email to coreos-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org
I would not. Ignition supports merging configuration files, wherein the child (typically) overwrites the parent. This means that you can have a "general" configuration, and merge in other configuration files to provide for node-specific configuration.
I'm not sure if there is any additional relevant documentation beyond the Operator Notes documentation:
https://github.com/coreos/ignition/blob/master/doc/operator-notes.md#config-...
On 1/22/20 12:20 PM, Thomas Schneider wrote:
Hi,
my understanding of your reply is that any additional software required should run in container(s).
With regards to qemu-guest-agent my understanding is that it was decided not to include it in FCOS. However I can install it if I think it's needed. Btw, qemu-guest-agent works as expected the way I installed it.
My question with regards to the other packages (ncdu, nano, ...) installed: Do you recommend to revert this installation?
It depends on what you need them for. I think jlebon is trying to say that for most things you can run them in a local toolbox container so they don't pollute the host, so if you can do that, it would be preferable so automatic updates don't break you.
And what about K8S? I found many documenation (e.g. here https://github.com/coreos/coreos-kubernetes/blob/master/Documentation/kubernetes-on-baremetal.md) for the installation of K8S on CoreOS. But ultimately they are pointing to using "Tectonic". If I don't want to use "Tectonic" (for whatever reason), are there any other options? Can I use this https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/ K8S getting started guide (from K8S project)?
We don't have a good answer for K8S right now. Different users have figured out how to run it, but we don't have any published documentation for doing that yet. We were just trying to get the base OS out the door first. Here is an issue to follow: https://github.com/coreos/fedora-coreos-tracker/issues/93
coreos@lists.fedoraproject.org