Zen

Source string Source string

176/10000 · 176

The string is read only.

English Actions
How are Fedora CoreOS nodes provisioned? Can I re-use existing cloud-init configurations?
Fedora CoreOS is provisioned with Ignition. Existing cloud-init configurations are not supported and will need to be migrated into their Ignition equivalent.
What data persists across upgrades and reboots?
The directories `/etc` and `/var` are mounted as read-write which lets users write and modify files.
The directory `/etc` may be changed by deployments, but will not override user made changes. The content under `/var` is left untouched by rpm-ostree when applying upgrades or rollbacks. For more information, refer to the https://docs.fedoraproject.org/en-US/fedora-coreos/storage/#_mounted_filesystems[Mounted Filesystems] section.
Which container runtimes are available on Fedora CoreOS?
Fedora CoreOS includes Docker and podman by default. Based on community engagement and support this list could change over time.
Can I run Kubernetes on Fedora CoreOS?
Yes. However, Fedora CoreOS does not include a specific container orchestrator (or version of Kubernetes) by default.
How do I run custom applications on Fedora CoreOS?
On Fedora CoreOS, containers are the way to install and configure any software not provided by the base operating system. The package layering mechanism provided by rpm-ostree will continue to exist for use in debugging a Fedora CoreOS machine, but we strongly discourage its use. For more about this, please refer to xref:running-containers.adoc[documentation].
Where is my preferred tool for troubleshooting?
The FCOS image is kept minimal by design. Not every troubleshooting tool are included by default. Instead, it is recommended to use the `toolbox` utility.
xref:debugging-with-toolbox.adoc[Debugging with Toolbx].
How do I coordinate cluster-wide OS updates?
The Zincati update manager includes a https://coreos.github.io/zincati/usage/updates-strategy/#lock-based-strategy[lock-based updates strategy] that supports multiple backends.
OKD's https://github.com/openshift/machine-config-operator[Machine Config Operator (MCO)] automatically handles updates of Fedora CoreOS in OKD clusters. The MCO additionally covers reconciliation of machine configuration changes.
How do I upload Fedora CoreOS to private AWS EC2 regions?
Fedora CoreOS today is only uploaded to the standard AWS regions. For regions in other AWS partitions like GovCloud and AWS China, you must upload the images yourself.
Note that Fedora CoreOS uses a unified BIOS/UEFI partition layout. As such, it is not compatible with the `aws ec2 import-image` API (for more information, see https://github.com/openshift/os/pull/396[related discussions]). Instead, you must use `aws ec2 import-snapshot` combined with `aws ec2 register-image`.
To learn more about these APIs, see the AWS documentation for https://docs.aws.amazon.com/vm-import/latest/userguide/vmimport-import-snapshot.html[importing snapshots] and https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/creating-an-ami-ebs.html#creating-launching-ami-from-snapshot[creating EBS-backed AMIs].
Can I run containers via docker and podman at the same time?
No. Running containers via `docker` and `podman` at the same time can cause issues and unexpected behavior. We highly recommend against trying to use them both at the same time.
It is worth noting that in Fedora CoreOS we have `docker.service` disabled by default but it is easily started if anything communicates with the `/var/run/docker.sock` because `docker.socket` is enabled by default. This means that if a user runs any `docker` command (via `sudo docker`) then the daemon will be activated.
In https://github.com/coreos/fedora-coreos-tracker/issues/408[coreos/fedora-coreos-tracker#408] it was pointed out that because of socket activation users who are using `podman` for containers could unintentionally start the docker daemon. This could weaken the security of the system because of the interaction of both container runtimes with the firewall on the system. To prevent making this mistake you can disable `docker` completely by masking the `docker.service` systemd unit.
Example Butane config for disabling docker.service
variant: fcos
version: {butane-latest-stable-spec}
systemd:
units:
- name: docker.service
mask: true
Are Fedora CoreOS x86_64 disk images hybrid BIOS+UEFI bootable?
The x86_64 images we provide can be used for either BIOS (legacy) boot or UEFI boot. They contain a hybrid BIOS/UEFI partition setup that allows them to be used for either. The exception to that is the `metal4k` 4k native image, which is targeted at disks with 4k sectors and https://github.com/coreos/coreos-assembler/blob/12029fea7798fa5d3535eafcf8c3d02f9a6095e4/src/cmd-buildextend-metal#L200-L202[does not have a BIOS boot partition] because 4k native disks are https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/hard-drives-and-partitions#advanced-format-drives[only supported with UEFI].
What's the difference between Ignition and Butane configurations?
Ignition configuration is a low-level interface used to define the whole set of customizations for an instance. It is primarily meant as a machine-friendly interface, with content encoded as JSON and a fixed structure defined via JSON Schema. This JSON configuration is processed by each FCOS instance upon first boot.

Loading…

User avatar None

String updated in the repository
The Zincati update manager includes a https://coreos.github.io/zincati/usage/updates-strategy/#lock-based-strategy[lock-based updates strategy] that supports multiple backends.
The Zincati update manager includes a https://coreos.github.io/zincati/usage/updates-strategy/#lock-based-strategy[lock-based updates strategy] that supports multiple backends.
a year ago
Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:
Consecutive duplicated words: French, French

Reset

Glossary

English English
No related strings found in the glossary.

14669243 String information

Source string description
type: Plain text
Flags
placeholders:r"`[\w.\/\-_=@&*:$●+~()\] ]*`", read-only
Source string location
./pages/faq.adoc:101
String age
a year ago
Last updated
a year ago
Source string age
a year ago
Translation file
pot/master/pages/faq.pot, string 36