From 21ec3c517422bf7df89d2894b6d0ca7d062a5710 Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Thu, 5 Dec 2024 11:56:12 -0500 Subject: [PATCH] spec: create/own /etc/containers/networks In some cases if /etc/ is mounted read-only the non-existence of the `/etc/containers/networks` directory will cause basic functionality to fail. ``` bash-5.2# mount --bind -o ro /etc/containers/ /etc/containers/ bash-5.2# podman info Error: mkdir /etc/containers/networks: read-only file system ``` Since it's going to get created anyway let's just have the directory exist from the beginning. --- rpm/containers-common.spec | 1 + 1 file changed, 1 insertion(+) diff --git a/rpm/containers-common.spec b/rpm/containers-common.spec index 125a1b62d..6146eb581 100644 --- a/rpm/containers-common.spec +++ b/rpm/containers-common.spec @@ -187,6 +187,7 @@ ln -s ../../../..%{_sysconfdir}/yum.repos.d/redhat.repo %{buildroot}%{_datadir}/ %files %dir %{_sysconfdir}/containers %dir %{_sysconfdir}/containers/certs.d +%dir %{_sysconfdir}/containers/networks %dir %{_sysconfdir}/containers/oci %dir %{_sysconfdir}/containers/oci/hooks.d %dir %{_sysconfdir}/containers/registries.conf.d