Mentioning nuances around the term

[azarboon]

Marc Brooker has written a blog post explaining that "container" means different thing to different people, and that it should be checked whether audience and narrator use the same definition. Below are his four suggested definition. Given the authority of Docker, I suggest this nuance to be mentioned. So readers are more informed and take cautionary acts to ensure they are in sync with their audience. It can also prevent confusion / misunderstanding for non-experts. I've added it.

• An approach to packaging an application along with its dependencies (sometimes a whole operating system user space), that can then run on a minimal runtime environment with a clear contract.
• A set of development, deployment, architectural, and operational approaches built around applications packaged this way.
• A set of operational, security, and performance isolation tools that allow multiple applications to share an operating system without interfering with each other. On Linux, this tools include chroot, cgroups, namespaces, seccomp, and others.
• A set of implementations of these practices (the proper nouns, Docker, Kubernetes, ECS, etc).

Related issues or tickets

Reviews

• Technical review
• Editorial review
• Product review

[netlify]

✅ Deploy Preview for docsdocker ready!

Name	Link
🔨 Latest commit	1a31bd4
🔍 Latest deploy log	https://app.netlify.com/sites/docsdocker/deploys/670a2f006986b9000807991a
😎 Deploy Preview	https://deploy-preview-21109--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 configuration.

[dvdksn]

I don't think this is helpful. I think the only thing this does is add ambiguity; these docs are, as you say, authoritative.

[docker-robot]

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