engine: clarfiy daemon.json configuration for logging drivers

[dvdksn]

Proposed changes

Clarify the location of daemon.json (differences between DD and Docker Engine) for configuring logging drivers on Docker Engine.

Related issues (optional)

#15106

[netlify]

✅ Deploy Preview for docsdocker ready!

Name	Link
🔨 Latest commit	234665d
🔍 Latest deploy log	https://app.netlify.com/sites/docsdocker/deploys/63ff191ac6ccba0008d1a993
😎 Deploy Preview	https://deploy-preview-16752--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.

[thaJeztah]

Hmm.. browsing the previous, I'm now wondered if we're still sending users back-and-forth now (bear with me);

On the page, we show links to "how to configure the daemon" (for desktop (mac/win/linux) or standalone);

When clicking the "Desktop" links, it brings me to a section only describing where to set the daemon.json on Desktop, but no information "what to set there"

And for "standalone", it brings me on another "round-trip"

[thaJeztah]

Wondering if we need to better separate "how to set the daemon.json", and "what to set in the daemon.json" 🤔

[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

[dvdksn]

Closing this one in favor of a bigger refactoring of the daemon/config docs (I'm sure we will get to it at some point... 😄 )