-
Bug
-
Resolution: Duplicate
-
Undefined
-
None
-
4.15
-
None
-
No
-
False
-
Description of problem: While debugging a (probably) separate issue, I noticed that my coredns-monitor container was complaining every 30s about failing to read the /run/nodeip-configuration/ipv4 file. As seen in this log file :
time="2023-12-07T06:22:55Z" level=info msg="Failed to read ip from file /run/nodeip-configuration/ipv4" error="open /run/nodeip-configuration/ipv4: no such file or directory" time="2023-12-07T06:23:25Z" level=info msg="Failed to read ip from file /run/nodeip-configuration/ipv4" error="open /run/nodeip-configuration/ipv4: no such file or directory" time="2023-12-07T06:23:55Z" level=info msg="Failed to read ip from file /run/nodeip-configuration/ipv4" error="open /run/nodeip-configuration/ipv4: no such file or directory" time="2023-12-07T06:24:25Z" level=info msg="Failed to read ip from file /run/nodeip-configuration/ipv4" error="open /run/nodeip-configuration/ipv4: no such file or directory"
While the host has a /run/nodeip-configuration/ipv4 file, the container does not bind-mount it. Should it?
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
