[操作系统/Linux] Rocky Linux 使用指南
0 序
-
接续: [操作系统/CENTOS/Rocky/Ubuntu] Linux 发行版操作系统-深度对比 - 博客园/千千寰宇
-
作为软件开发人员,原先是 CENTOS 的重度用户。需要了解、使用 Rocky Linux 的常用命令,包括但不限于:软件包的安装、查看/检索、卸载、...。为此梳理、小结至此处。
1 使用指南
作为从 CentOS 转来的软件开发者,好消息是 Rocky 就是 RHEL 系,你的所有 CentOS 命令基本照用,唯一变化是
yum已完全由dnf取代(两者命令几乎同构)。下面是高频命令速查。
软件包管理(dnf)
| 操作 | 命令 |
|---|---|
| 安装(自动确认) | sudo dnf install -y <包名> |
| 本地/在线检索包名 | dnf search <关键词> |
| 查看已装包 | dnf list installed |
| 查看可升级包 | dnf list upgrades |
| 查看某包详情 | dnf info <包名> |
| 查看某文件属于哪个包 | dnf provides <路径>(如 */shturl.cc) |
| 卸载 | sudo dnf remove <包名> |
| 卸载并清依赖 | sudo dnf autoremove |
| 升级系统 | sudo dnf update / sudo dnf upgrade |
| 安装本地 rpm | sudo dnf install ./x.rpm |
| 清缓存 | sudo dnf clean all |
- 本地/在线检索包名
[root@xxx ~]# dnf search curl
Last metadata expiration check: 2:46:08 ago on Thu 15 Oct 2026 02:38:01 PM CST.
=========================================================================================================================================================== Name Exactly Matched: curl ===========================================================================================================================================================
curl.x86_64 : A utility for getting files from remote servers (FTP, HTTP, and others)
========================================================================================================================================================== Name & Summary Matched: curl ==========================================================================================================================================================
curl-minimal.x86_64 : Conservatively configured build of curl for minimal installations
libcurl-devel.i686 : Files needed for building applications with libcurl
libcurl-devel.x86_64 : Files needed for building applications with libcurl
libcurl-minimal.i686 : Conservatively configured build of libcurl for minimal installations
libcurl-minimal.x86_64 : Conservatively configured build of libcurl for minimal installations
nbdkit-curl-plugin.x86_64 : HTTP/FTP (cURL) plugin for nbdkit
python3-pycurl.x86_64 : Python interface to libcurl for Python 3
qemu-kvm-block-curl.x86_64 : QEMU CURL block driver
=============================================================================================================================================================== Name Matched: curl ===============================================================================================================================================================
libcurl.i686 : A library for getting files from web servers
libcurl.x86_64 : A library for getting files from web servers
仓库管理
| 操作 | 命令 |
|---|---|
| 列出已启用仓库 | dnf repolist |
| 启用/禁用仓库 | dnf config-manager --set-enabled <repo> / --set-disabled |
| 添加 EPEL | sudo dnf install epel-release |
| 看某包来自哪个仓库 | dnf info <包名> 中 Repository 字段 |
- 列出已启用仓库
[root@xxx ~]# dnf info openssh
Rocky Linux 9 - Extras 930 B/s | 311 B 00:00
Errors during downloading metadata for repository 'extras':
- Status code: 403 for https://mirrors.aliyun.com/rockylinux/9/extras/x86_64/os/repodata/repomd.xml (IP: 59.80.28.219)
Error: Failed to download metadata for repo 'extras': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
[root@xxx-db ~]# dnf repolist
repo id repo name
appstream Rocky Linux 9 - AppStream
baseos Rocky Linux 9 - BaseOS
extras Rocky Linux 9 - Extras
[root@xxx ~]#
服务与开机项
| 操作 | 命令 |
|---|---|
| 启停/重启服务 | sudo systemctl start/stop/restart <服务> |
| 开机自启 | sudo systemctl enable --now <服务> |
| 查看状态 | systemctl status <服务> |
| 查看失败单元 | systemctl --failed |
- 查看状态:
systemctl status <服务>
[root@xxx ~]# systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/etc/systemd/system/docker.service; enabled; preset: disabled)
Active: active (running) since Tue 2026-09-15 09:15:57 CST; 4 weeks 2 days ago
Docs: https://docs.docker.com
Main PID: 987 (dockerd)
Tasks: 304 (limit: 203453)
Memory: 410.6M (peak: 762.4M)
CPU: 1h 53min 434ms
CGroup: /system.slice/docker.service
├─ 987 /usr/bin/dockerd
├─ 1689 containerd --config /var/run/docker/containerd/containerd.toml
├─ 2113 /usr/bin/containerd-shim-runc-v2 -namespace moby -id ec7e3c53b10b13dafea4b64b12d4edcf0f135c383037c9d466986360b87adfda -address /var/run/docker/containerd/containerd.sock
├─ 2144 /usr/bin/containerd-shim-runc-v2 -namespace moby -id 369aa62d90b339f033388b89ebaffadba629344f957fb221ef9fd7056a9ef195 -address /var/run/docker/containerd/containerd.sock
├─ 2190 /usr/bin/containerd-shim-runc-v2 -namespace moby -id 2c0bf22084b0ece9f824e0a7c35a31e6e6954dda364c9396dd9b4f787df4af45 -address /var/run/docker/containerd/containerd.sock
├─ 2275 /usr/bin/containerd-shim-runc-v2 -namespace moby -id b732f3839c324e9f3dd03a3c73c7a74dc2c8998c6969676c53627a018032ebe1 -address /var/run/docker/containerd/containerd.sock
├─ 2429 /usr/bin/containerd-shim-runc-v2 -namespace moby -id 09d465ae2dd9df620e8900ace8b97ecba66f0827838b5fbb321c69c4f1dbcdd4 -address /var/run/docker/containerd/containerd.sock
├─ 2514 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 5432 -container-ip 172.21.0.2 -container-port 5432 -use-listen-fd
├─ 2528 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 5432 -container-ip 172.21.0.2 -container-port 5432 -use-listen-fd
├─ 2552 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 1433 -container-ip 172.21.0.3 -container-port 1433 -use-listen-fd
├─ 2559 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 1433 -container-ip 172.21.0.3 -container-port 1433 -use-listen-fd
├─ 2648 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 1729 -container-ip 172.21.0.4 -container-port 1729 -use-listen-fd
├─ 2653 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 1729 -container-ip 172.21.0.4 -container-port 1729 -use-listen-fd
├─ 2670 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 8000 -container-ip 172.21.0.4 -container-port 8000 -use-listen-fd
├─ 2677 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 8000 -container-ip 172.21.0.4 -container-port 8000 -use-listen-fd
├─ 2711 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 9092 -container-ip 172.21.0.5 -container-port 9092 -use-listen-fd
├─ 2717 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 9092 -container-ip 172.21.0.5 -container-port 9092 -use-listen-fd
├─ 2734 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 9999 -container-ip 172.21.0.5 -container-port 9999 -use-listen-fd
├─ 2741 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 9999 -container-ip 172.21.0.5 -container-port 9999 -use-listen-fd
├─ 2796 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 3306 -container-ip 172.21.0.7 -container-port 3306 -use-listen-fd
├─ 2801 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 3306 -container-ip 172.21.0.7 -container-port 3306 -use-listen-fd
├─ 10775 /usr/bin/containerd-shim-runc-v2 -namespace moby -id e289f386b6d41fb057fcbdc0be2219b86f71c8273ce8216308b65301f2c3b33d -address /var/run/docker/containerd/containerd.sock
├─ 10856 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 2181 -container-ip 172.22.0.2 -container-port 2181 -use-listen-fd
├─ 10862 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 2181 -container-ip 172.22.0.2 -container-port 2181 -use-listen-fd
├─ 10878 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 8080 -container-ip 172.22.0.2 -container-port 8080 -use-listen-fd
├─ 10885 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 8080 -container-ip 172.22.0.2 -container-port 8080 -use-listen-fd
├─1843201 /usr/bin/containerd-shim-runc-v2 -namespace moby -id 87b380f9995bf75c7f796a0d24ac35c4123ed48585f1160b0c2c464981024003 -address /var/run/docker/containerd/containerd.sock
├─1843281 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 5236 -container-ip 172.24.0.2 -container-port 5236 -use-listen-fd
└─1843287 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 5236 -container-ip 172.24.0.2 -container-port 5236 -use-listen-fd
Oct 15 13:58:54 xxx dockerd[1689]: time="2026-10-15T13:58:54.716083267+08:00" level=info msg="shim disconnected" id=d2720aa3bb3211f3a37b4375a36481a2108eabadd72a45f81def2543f0a56531 namespace=moby
Oct 15 13:58:54 xxx dockerd[1689]: time="2026-10-15T13:58:54.716121095+08:00" level=info msg="cleaning up after shim disconnected" id=d2720aa3bb3211f3a37b4375a36481a2108eabadd72a45f81def2543f0a56531 namespace=moby
Oct 15 13:58:54 xxx dockerd[1689]: time="2026-10-15T13:58:54.716132281+08:00" level=info msg="cleaning up dead shim" id=d2720aa3bb3211f3a37b4375a36481a2108eabadd72a45f81def2543f0a56531 namespace=moby
Oct 15 13:58:54 xxx dockerd[987]: time="2026-10-15T13:58:54.716136764+08:00" level=info msg="received task-delete event from containerd" container=d2720aa3bb3211f3a37b4375a36481a2108eabadd72a45f81def2543f0a56531 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Oct 15 14:06:48 xxx dockerd[987]: time="2026-10-15T14:06:48.193925897+08:00" level=info msg="stopping restart-manager" container=0299c4f7181fecada269776f957445b5f4746ccad486e704d54e37b4f4be8c6f
Oct 15 14:06:50 xxx dockerd[1689]: time="2026-10-15T14:06:50.546964166+08:00" level=info msg="shim disconnected" id=0299c4f7181fecada269776f957445b5f4746ccad486e704d54e37b4f4be8c6f namespace=moby
Oct 15 14:06:50 xxx dockerd[1689]: time="2026-10-15T14:06:50.547009429+08:00" level=info msg="cleaning up after shim disconnected" id=0299c4f7181fecada269776f957445b5f4746ccad486e704d54e37b4f4be8c6f namespace=moby
Oct 15 14:06:50 xxx dockerd[1689]: time="2026-10-15T14:06:50.547027319+08:00" level=info msg="cleaning up dead shim" id=0299c4f7181fecada269776f957445b5f4746ccad486e704d54e37b4f4be8c6f namespace=moby
Oct 15 14:06:50 xxx dockerd[987]: time="2026-10-15T14:06:50.547135696+08:00" level=info msg="received task-delete event from containerd" container=0299c4f7181fecada269776f957445b5f4746ccad486e704d54e37b4f4be8c6f module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Oct 15 16:22:07 xxx dockerd[987]: time="2026-10-15T16:22:07.905980225+08:00" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:192.168.11.111:54565" dns-server="udp:8.8.8.8:53" error="read udp 192.168.11.111:54565->8.8.8.8:53: i/o timeout" question=";us.i.posthog.com.\tIN\t AAAA"
安全与防火墙
| 操作 | 命令 |
|---|---|
| 防火墙放行 | sudo firewall-cmd --add-port=8080/tcp --permanent && sudo firewall-cmd --reload |
| 查看 SELinux 状态 | getenforce |
| 临时/永久关闭 SELinux | setenforce 0;改 /etc/selinux/config 中 SELINUX=disabled |
| 查看端口监听 | ss -tlnp |
开发常用
| 操作 | 命令 |
|---|---|
| 装开发工具链 | sudo dnf groupinstall "Development Tools" |
| 装 Python3 | sudo dnf install python3 python3-pip |
| 装 GCC/编译器 | sudo dnf install gcc gcc-c++ make |
| 装 Git | sudo dnf install git |
| 版本内核信息 | uname -r |
提醒:安装 OpenStack/数据库/中间件时,优先先启用 epel-release 并查 dnf search,避免装到过期源里的旧版本。
查看本机IP
Z FAQ for Rocky Linux
Q: Rocky Linux 9.7 是基于centos 7还是centos 8构建的?
- 结论:Rocky Linux 9.7 既不是基于 CentOS 7,也不是基于 CentOS 8,而是对应 RHEL 9.7。
准确的血缘关系
Rocky Linux 的定位是 RHEL 的下游二进制兼容重建版,版本号直接跟 RHEL 对齐:
- Rocky Linux 8.x → RHEL 8 → 对应 CentOS 8
- Rocky Linux 9.x → RHEL 9 → 无传统 CentOS 9 稳定版(只有 CentOS Stream 9)
- Rocky Linux 10.x → RHEL 10
Rocky Linux 9.7 官方发布说明也明确它是 RHEL 9.7 的免费替代版,可作 CentOS 9 Stream 的替换对象。
为什么不是 CentOS 7
CentOS 官方文档写得很清楚:CentOS Linux 是 RHEL 的 rebuild,版本号跟着 RHEL 走。
- CentOS 7 ≈ RHEL 7
- CentOS 8 ≈ RHEL 8
Rocky 9 属于 el9 基线(glibc 2.34、Python 3.9、OpenSSL 3.0),跟 CentOS 7 的 el7 基线(glibc 2.17、Python 2.7/3.6)完全不是一条线。
为什么也不算「基于 CentOS 8」
- CentOS 8 本身只是 RHEL 8 的重建;而 Rocky 9 的上游是 RHEL 9 源码,不是 CentOS 8 的包。
RHEL 8 的下游重建 = CENTOS 8
RHEL 9 = Rocky 9 的上游
- 另外,传统 CentOS Linux 在 8 之后就停了(CentOS 8 EOL 2021-12-31),Red Hat 把重心转到
CentOS Stream,所以并不存在「CentOS 9 稳定版」可拿来当【构建基础】。
💡 更准确的说法:
Rocky 9继承了 CentOS Linux 作为RHEL下游重建 的那条路线,而不是继承自某一个具体的 CentOS 大版本。
迁移视角的提醒
如果你现在在 CentOS 7 上,想换到 Rocky:
- 直接上 Rocky 9 跨度较大(systemd、glibc、Python、SELinux 策略都变)
- 稳妥路径一般是 CentOS 7 → Rocky 8 → 再升 Rocky 9
Rocky Linux不支持跨大版本原地升级,8→9 建议重装
小结:Rocky 9.7 = RHEL 9.7 的克隆,跟 CentOS 7 无关,也比 CentOS 8 高一代。
Y 推荐文献
X 参考文献
本文链接: https://www.cnblogs.com/johnnyzen
关于博文:评论和私信会在第一时间回复,或直接私信我。
版权声明:本博客所有文章除特别声明外,均采用 BY-NC-SA 许可协议。转载请注明出处!
日常交流:大数据与软件开发-QQ交流群: 774386015 【入群二维码】参见左下角。您的支持、鼓励是博主技术写作的重要动力!

浙公网安备 33010602011771号