podman machine: Adjust Chrony makestep config

This allows Chrony to update the system time when it has drifted far
from NTP time. By default Chrony only makes slight adjustments, but in
the case where a user's laptop lid has been shut for a while and then
the machine is resumed, the VM system time could be hours or days behind
real time, and it may never catch up if Chrony only makes slight
changes.

[NO NEW TESTS NEEDED]

Fixes containers#11541

Signed-off-by: Jordan Christiansen <xordspar0@gmail.com>

pkg/machine/ignition.go

@@ -513,6 +513,34 @@ Delegate=memory pids cpu io
 		}
 	}
 
+	files = append(files, File{
+		Node: Node{
+			User:  getNodeUsr("root"),
+			Group: getNodeGrp("root"),
+			Path:  "/etc/chrony.conf",
+		},
+		FileEmbedded1: FileEmbedded1{
+			Append: []Resource{{
+				Source: encodeDataURLPtr("\nconfdir /etc/chrony.d\n"),
+			}},
+		},
+	})
+
+	// Issue #11541: allow Chrony to update the system time when it has drifted
+	// far from NTP time.
+	files = append(files, File{
+		Node: Node{
+			User:  getNodeUsr("root"),
+			Group: getNodeGrp("root"),
+			Path:  "/etc/chrony.d/50-podman-makestep.conf",
+		},
+		FileEmbedded1: FileEmbedded1{
+			Contents: Resource{
+				Source: encodeDataURLPtr("makestep 1 -1\n"),
+			},
+		},
+	})
+
 	return files
 }