Skip to content

Move old RHEL network manager info into admonition #498

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 27, 2025
Merged

Move old RHEL network manager info into admonition #498

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
243297b
Move network manager disable into a admonition
dereknola Oct 24, 2025
b0ed724
Move nm disable into admonition
dereknola Oct 24, 2025
33a8340
Truncate sysbox blog
dereknola Oct 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion blog/2025-09-27-k3s-sysbox.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,12 +2,14 @@
title: Sysbox Runtime With K3s
description: Integrating sysbox runtime with k3s' containerd
authors: husseingalal
tags: ["runc","k3s","sysbox"]
tags: ["runc","sysbox"]
hide_table_of_contents: true
---

The K3s binary bundles all the components needed to run a production-ready, CNCF-conformant Kubernetes cluster including containerd, runc, kubelet, and more. In this post we will discuss how containerd communicates with OCI runtimes and will discuss adding another container runtime (Sysbox) to K3s and how it can be used to run system pods in your environment.

<!-- truncate -->

## Containerd and Runc

First we need to talk briefly about how containerd works with runc. Containerd is a long running daemon that is responsible for:
Expand Down
6 changes: 5 additions & 1 deletion docs/installation/requirements.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,11 +66,15 @@ firewall-cmd --reload

Additional ports may need to be opened depending on your setup. See [Inbound Rules](#inbound-rules-for-k3s-nodes) for more information. If you change the default CIDR for pods or services, you will need to update the firewall rules accordingly.

If enabled, it is required to disable nm-cloud-setup and reboot the node:
:::warning Older RHEL/CentOS Releases

OS versions prior to RHEL 8.4 carry NetworkManager with a known bug that interferes with K3s networking. If using an older release, it is required to disable nm-cloud-setup and reboot the node:
```bash
systemctl disable nm-cloud-setup.service nm-cloud-setup.timer
reboot
```
:::

</TabItem>
<TabItem value="debian" label="Ubuntu / Debian">

Expand Down
Loading