From 24a521302a8092660e0aa88715ca0c2566c89bfb Mon Sep 17 00:00:00 2001
From: Dean Chen <862469039@qq.com>
Date: Tue, 18 Aug 2026 18:42:03 +0500
Subject: [PATCH] docs: note X-Meta- headers are forwarded to the registry

HttpHeaders go on client-to-daemon calls. Names that start with
X-Meta- are also passed through on pull and similar.

Signed-off-by: Dean Chen <862469039@qq.com>
---
 docs/reference/commandline/docker.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/docs/reference/commandline/docker.md b/docs/reference/commandline/docker.md
index 73ef948beae2..95b63074ad33 100644
--- a/docs/reference/commandline/docker.md
+++ b/docs/reference/commandline/docker.md
@@ -279,6 +279,11 @@ sent from the Docker client to the daemon. Docker doesn't try to interpret or
 understand these headers; it simply puts them into the messages. Docker does
 not allow these headers to change any headers it sets for itself.
 
+The daemon forwards headers whose names start with `X-Meta-` (for
+example `X-Meta-Trace`) to the registry on operations such as
+`docker pull`. Other custom headers stay on the client-to-daemon
+request and are not sent to the registry.
+
 Alternatively, use the `DOCKER_CUSTOM_HEADERS` [environment variable](#environment-variables),
 which is available in v27.1 and higher. This environment-variable is experimental,
 and its exact behavior may change.