build: add guides

[crazy-max]

follow-up #14644

needs docker/buildx#1140 so keeping in draft for now

Fetch build guides and bake from upstream buildx repo in https://github.com/docker/buildx/tree/master/docs/guides

[netlify]

✅ Deploy Preview for docsdocker ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	c492b57
🔍 Latest deploy log	https://app.netlify.com/sites/docsdocker/deploys/62d77c672426140009d9e84c
😎 Deploy Preview	https://deploy-preview-14905--docsdocker.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[dockertopia]

I think this should (all) be in manuals, we're listing feature and giving some samples. It's not an actual tutorial with a use case behind (as far as I can see) it.

[dockertopia]

I'm not sure what we're doing here, is this about removing something from the docs that is some repo? If so, I'm not sure that is the right way forward.

[crazy-max]

We are fetching markdown files from buildx repo in https://github.com/docker/buildx/tree/master/docs/guides (except ci-cd) and add them to build/guides folder here.
Will be available in Manuals > Docker Build > Guides. See https://deploy-preview-14905--docsdocker.netlify.app/build/guides/cni-networking/

[dockertopia]

@crazy-max I think we can move this asap to Build doc set, but I think it would make more sense to have it all in the Manuals to have users understand in one place all functionality BuildKit introduces. Build cmd might redirect to buildx but I'm not use if it's not more confusing for the users to change the guide to building with buildKit.

[crazy-max]

moving to draft as we might create stub files so we can maintain frontmatter section here. see #15165 for more info.

[jedevc]

This looks mostly good to me, I think we'd probably want to do some follow-ups to improve the consistency of our buildx docs - but it'll be good to have this info on the docs site I think.

[jedevc]

Ahh this seems strange to me, but not sure whether there's a better alternative.

Having a section in Manuals called Guides, when we have a Guides category 🤔 I feel like it's better to maybe be consistent with the rest of our docs for now, and put it into Guides?

Other options:

• Don't call them "Guides" but something like "Advanced usage"? But then of course, what happens if we add more entry-level guides/tutorials, do those go into the guides section (splitting them up), or do we keep them together, which seems inconsistent with the rest of the docs.
• Rework the buildkit guides to be more like the guides in the rest of the docs, by making them more tutorial like, etc - maybe the remote builder guide is already like this in style?

[jedevc]

We should group this near the kubernetes builder. Maybe we also want to call it <x>-driver instead of <x>-builder - really not sure on that though.

[jedevc]

Do we want to call out that bake is still experimental here as well?

[docker-robott]

Thanks for the pull request. We'd like to make our product docs better, but haven’t been able to review all the suggestions.
As our docs have also diverged, we do not have the bandwidth to review and rebase old pull requests.

If the updates are still relevant, review our contribution guidelines and rebase your pull request against the latest version of the docs, then mark it as fresh with a /remove-lifecycle stale comment.
If not, this pull request will be closed in 30 days. This helps our maintainers focus on the active pull requests.

Prevent pull requests from auto-closing with a /lifecycle frozen comment.

/lifecycle stale