Closed jbpratt closed 2 years ago
I am seeing a service start in a failed state
[kc2user@fedora-br0 ~]$ sudo journalctl -u ldconfig.service
-- Journal begins at Sat 2021-11-06 17:44:21 UTC, ends at Sat 2021-11-06 17:54:38 UTC. --
Nov 06 17:44:25 fedora systemd[1]: Starting Rebuild Dynamic Linker Cache...
Nov 06 17:44:26 fedora ldconfig[601]: /sbin/ldconfig: Cannot lstat /lib64/libperl.so.5.34.0: Permission denied
Nov 06 17:44:26 fedora ldconfig[601]: /sbin/ldconfig: Cannot lstat /lib64/libsodium.so.23.3.0: Permission denied
Nov 06 17:44:26 fedora ldconfig[601]: /sbin/ldconfig: Cannot lstat /lib64/libgpm.so.2.1.0: Permission denied
Nov 06 17:44:26 fedora ldconfig[601]: /sbin/ldconfig: Renaming of /etc/ld.so.cache~ to /etc/ld.so.cache failed: Permission denied
Nov 06 17:44:26 fedora systemd[1]: ldconfig.service: Main process exited, code=exited, status=1/FAILURE
Nov 06 17:44:26 fedora systemd[1]: ldconfig.service: Failed with result 'exit-code'.
Nov 06 17:44:26 fedora systemd[1]: Failed to start Rebuild Dynamic Linker Cache.
Duplicated the F34 workflow
tested this locally and published to
ghcr.io/jbpratt/fedora:35
One thing I'm not sure on is the two Fedora images (34, 35) will be fighting over the
latest
tag, should I remove that publish step from this workflow or update 34 to no longer push to latest?