Skip to content

Document custom HTTP header forwarding to registries - #26085

Open
Gaalbu wants to merge 1 commit into
docker:mainfrom
Gaalbu:docs/document-custom-http-header-prefix
Open

Gaalbu wants to merge 1 commit into
docker:mainfrom
Gaalbu:docs/document-custom-http-header-prefix

Conversation

@Gaalbu

@Gaalbu Gaalbu commented Sep 13, 2026

Copy link
Copy Markdown

Fixes #11456.

Clarify that the daemon forwards custom headers to registries only when their names start with X-Meta-, and update the sample configuration to use the working prefix.

The behavior is implemented in Moby's image and plugin routers, which filter forwarded metadata headers by this prefix.

Signed-off-by: Gaalbu <gabrielalbuquerquealencar@gmail.com>
@netlify

netlify Bot commented Sep 13, 2026

Copy link
Copy Markdown

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit 0b8646c
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/6aa61fffde5efb0008543ac1
😎 Deploy Preview https://deploy-preview-26085--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@Gaalbu

Gaalbu commented Sep 13, 2026

Copy link
Copy Markdown
Author

Friendly ping — this PR is ready for review whenever you have a chance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Configured "HttpHeaders" are not sent by Docker daemon

1 participant