Skip to content

[CF1] docker + WARP DNS #22214

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 6, 2025
Merged

[CF1] docker + WARP DNS #22214

merged 2 commits into from
May 6, 2025

Conversation

deadlypants1973
Copy link
Contributor

Summary

PCX-14091

Screenshots (optional)

Documentation checklist

  • The documentation style guide has been adhered to.
  • If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
  • Files which have changed name or location have been allocated redirects.

Copy link
Contributor

hyperlint-ai bot commented May 5, 2025

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.


PR Change Summary

Enhanced Docker documentation to include details on accessing WARP DNS from Docker containers and clarified networking options.

  • Added instructions for accessing WARP DNS from Docker containers.
  • Outlined the use of custom Docker networks and host networking for WARP DNS resolution.
  • Provided examples demonstrating DNS resolution with Docker networking modes.

Modified Files

  • src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/known-limitations.mdx

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

…rp/troubleshooting/known-limitations.mdx

Co-authored-by: Pedro Sousa <[email protected]>
@deadlypants1973 deadlypants1973 merged commit 2bb460f into production May 6, 2025
12 checks passed
@deadlypants1973 deadlypants1973 deleted the kate/fixes-dockerdns branch May 6, 2025 12:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants