Zen

Translation

Fedora CoreOS keeps the base image as simple and small as possible for security and maintainability reasons. That is why you should in general prefer the usage of `podman` containers over layering software. However, in some cases it is necessary to add software to the base OS itself. For example, drivers or VPN software are potential candidates because they are harder to containerize and may be brought in as extensions to the OS.
English type: Plain text
Fedora CoreOS keeps the base image as simple and small as possible for security and maintainability reasons. That is why you should in general prefer the usage of `podman` containers over layering software. However, in some cases it is necessary to add software to the base OS itself. For example, drivers or VPN software are potential candidates because they are harder to containerize and may be brought in as extensions to the OS.
228/4330 · 433

Sign in to save translations.

English Spanish Actions
Adding OS extensions to the host system
Añadir extensiones de SO al huésped del sistema
Fedora CoreOS keeps the base image as simple and small as possible for security and maintainability reasons. That is why you should in general prefer the usage of `podman` containers over layering software. However, in some cases it is necessary to add software to the base OS itself. For example, drivers or VPN software are potential candidates because they are harder to containerize and may be brought in as extensions to the OS.
Fedora CoreOS mantiene la imagen base los más sencilla y pequeña posible por razones de seguridad y mantenimiento. Esto es por lo que usted debería, en general, preferir la utilización de contenedores sobre el software de capas.
If you're making nontrivial changes to the base operating system, you may instead consider using https://docs.fedoraproject.org/en-US/bootc/[Fedora Bootc], which is oriented around custom OS builds derived from a starting base image. There is more information on the relationship between Fedora CoreOS and Fedora Bootc in xref:faq.adoc#_how_does_fedora_coreos_relate_to_fedora_bootc[our FAQ].
 
To add in additional software to a Fedora CoreOS system, you can use https://coreos.github.io/rpm-ostree/[`rpm-ostree install`]. Consider these packages as "extensions": they extend the functionality of the base OS rather than e.g. providing runtimes for user applications. That said, there are no restrictions on which packages one can actually install. By default, packages are downloaded from the https://docs.fedoraproject.org/en-US/quick-docs/repositories/[Fedora repositories].
Para hacer esto, puede usar https://coreos.github.io/rpm-ostree/[`rpm-ostree install`]. Considere estos paquetes como "extensiones": ellos extienden la funcionalidad del SO base en lugar de, por ejemplo, proporcionar tiempos de ejecución para aplicaciones de usuario. Esto significa, que no hay restricciones en los paquetes que uno puede instalar actualmente. De modo predeterminado, los paquetes son descargados de los https://docs.fedoraproject.org/en-US/quick-docs/repositories/[repositorios Fedora].
To start the layering of a package, you need to write a systemd unit that executes the `rpm-ostree` command to install the wanted package(s). Changes are applied to a new deployment and a reboot is necessary for those to take effect.
Para iniciar la estratificación de un paquete, usted necesita escribir una unidad systemd que ejecute el comando `rpm-ostree` para instalar el paquete(s) deseado. De forma predeterminada, con `rpm-ostree install`, los cambios quedan en cola para el próximo arranque. Se puede usar la opción `-A/--apply-live` para aplicar los cambios en vivo *y* hacerlos persistentes.
Example: Layering vim and setting it as the default editor
Ejemplo: Estratificar vim y establecerlo como editor predeterminado
Fedora CoreOS includes both `nano` and `vi` as text editors, with the former set as default (see the corresponding https://fedoraproject.org/wiki/Changes/UseNanoByDefault[Fedora change]).
Fedora CoreOS incluye como editores de texto `nano` y `vi`, con el primero establecido como predeterminado (vea el correspondiente https://fedoraproject.org/wiki/Changes/UseNanoByDefault[cambio Fedora]).
This example shows how to install the fully fledged `vim` text editor and how to set it up as default for all users by setting up the required configuration in `/etc/profile.d/`.
Este ejemplo muestra como instalar el editor de texto `vim` completo y como configurarlo como predeterminado para todos los usuarios estableciendo la configuración requerida en `/etc/profile.d/`.
In the future, we will have a more Ignition-friendly method of doing this with stronger guarantees. See upstream issues https://github.com/coreos/butane/issues/81[butane#81] and https://github.com/coreos/fedora-coreos-tracker/issues/681[fedora-coreos-tracker#681] for more information.
 
variant: fcos
version: {butane-latest-stable-spec}
systemd:
units:
# Installing vim as a layered package with rpm-ostree
- name: rpm-ostree-install-vim.service
enabled: true
contents: |
[Unit]
Description=Layer vim with rpm-ostree
Wants=network-online.target
After=network-online.target
# We run before `zincati.service` to avoid conflicting rpm-ostree
# transactions.
Before=zincati.service
ConditionPathExists=!/var/lib/%N.stamp
 
[Service]
Type=oneshot
RemainAfterExit=yes
# `--allow-inactive` ensures that rpm-ostree does not return an error
# if the package is already installed. This is useful if the package is
# added to the root image in a future Fedora CoreOS release as it will
# prevent the service from failing.
ExecStart=/usr/bin/rpm-ostree install -y --allow-inactive vim
ExecStart=/bin/touch /var/lib/%N.stamp
ExecStart=/bin/systemctl --no-block reboot
 
[Install]
WantedBy=multi-user.target
storage:
files:
# Set vim as default editor
# We use `zz-` as prefix to make sure this is processed last in order to
# override any previously set defaults.
- path: /etc/profile.d/zz-default-editor.sh
overwrite: true
contents:
inline: |
export EDITOR=vim
 

Loading…

User avatar None

String added in the repository
Fedora CoreOS keeps the base image as simple and small as possible for security and maintainability reasons. That is why you should in general prefer the usage of `podman` containers over layering software. However, in some cases it is necessary to add software to the base OS itself. For example, drivers or VPN software are potential candidates because they are harder to containerize and may be brought in as extensions to the OS.
Fedora CoreOS mantiene la imagen base los más sencilla y pequeña posible por razones de seguridad y mantenimiento. Esto es por lo que usted debería, en general, preferir la utilización de contenedores sobre el software de capas.
a week ago
User avatar None

Source string changed
Fedora CoreOS keeps the base image as simple and small as possible for security and maintainability reasons. That is why you should in general prefer the usage of `podman` containers over layering software. However, in some cases it is necessary to add software to the base OS itself. For example, drivers or VPN software are potential candidates because they are harder to containerize and may be brought in as extensions to the OS.
a week ago
Browse all string changes

Things to check

Placeholders

The following format strings are missing: `podman`

Reset

Glossary

English Spanish
No related strings found in the glossary.

19111371 String information

Source string description
type: Plain text
Flags
placeholders:r"`[\w.\/\-_=@&*:$●+~()\] ]*`"
Source string location
pages/os-extensions.adoc:4
String age
a week ago
Last updated
a week ago
Source string age
a week ago
Translation file
po/es/master/pages/os-extensions.po, string 2