diff --git a/sdk_container/src/third_party/coreos-overlay/coreos/user-patches/sys-apps/systemd/0001-handle-missing-machine-id.patch b/sdk_container/src/third_party/coreos-overlay/coreos/user-patches/sys-apps/systemd/0001-handle-missing-machine-id.patch
new file mode 100644
index 0000000000..431957d827
--- /dev/null
+++ b/sdk_container/src/third_party/coreos-overlay/coreos/user-patches/sys-apps/systemd/0001-handle-missing-machine-id.patch
@@ -0,0 +1,34 @@
+This can be dropped in v285.5+.
+
+From b1d53ddea750f761234c2d8fb04b10f23f77347e Mon Sep 17 00:00:00 2001
+From: Justin Kromlinger <hashworks@archlinux.org>
+Date: Wed, 8 Oct 2025 16:55:09 +0200
+Subject: [PATCH] Drop `machine-id` OSC event field if /etc/machine-id doesn't
+ exist
+
+While we can safely assume that `/proc/sys/kernel/random/boot_id`
+exists, the same can't be said for `/etc/machine-id` in environments
+where systemd is installed, but not running. An example would be OCI
+containers like with the official Arch Linux image, see [0].
+
+Without this check the prompt would constantly output `/etc/machine-id:
+no such file or directory` with the OSC events introduced in dadbb34
+(v258).
+
+[0] https://gitlab.archlinux.org/archlinux/archlinux-docker/-/issues/107
+
+(cherry picked from commit 0fe45b98dd737da86fcbb703809ebf2163c397f3)
+--- a/profile.d/80-systemd-osc-context.sh
++++ b/profile.d/80-systemd-osc-context.sh
+@@ -32,7 +32,10 @@ __systemd_osc_context_escape() {
+ }
+ 
+ __systemd_osc_context_common() {
+-    printf ";user=%s;hostname=%s;machineid=%s;bootid=%s;pid=%s" "$USER" "$HOSTNAME" "$(</etc/machine-id)" "$(</proc/sys/kernel/random/boot_id)" "$$"
++    if [ -f /etc/machine-id ]; then
++        printf ";machineid=%s" "$(</etc/machine-id)"
++    fi
++    printf ";user=%s;hostname=%s;bootid=%s;pid=%s" "$USER" "$HOSTNAME" "$(</proc/sys/kernel/random/boot_id)" "$$"
+ }
+ 
+ __systemd_osc_context_precmdline() {