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. Signed-off-by: Dusty Mabe <[email protected]>
containers · Dec 5, 2024 · aa7bc16 · aa7bc16
1 parent 324d166
commit aa7bc16
Showing 1 changed file with 1 addition and 0 deletions.
diff --git 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