docs: add mention of support for containers without package managers to versioned_docs

website/versioned_docs/version-v0.1.x/introduction.md

@@ -36,10 +36,11 @@ This approach is motivated by the core principles of making direct container pat
 
 - **Copa supports patching _existing_ container images**.
   - Devs don't need to build their images using specific tools or modify them in some way just to support container patching.
+- **Copa supports containers without package managers _including_ distroless containers**
 - **Copa works with the existing vulnerability scanning and mitigation ecosystems**.
   - Image publishers don't need to create new workflows for container patching since Copa supports patching container images using the security update packages already being published today.
   - Consumers do not need to migrate to a new and potentially more limited support ecosystem for custom distros or change their container vulnerability scanning pipelines to include remediation, since Copa can be integrated seamlessly as an extra step to patch containers based on those scanning reports.
 - **Copa reduces the technical expertise needed and waiting on dependencies needed to patch an image**.
   - For OS package vulnerabilities, no specialized knowledge about a specific image is needed to be patch it as Copa relies on the vulnerability remediation knowledge already embedded in the reports produced by popular container scanning tools today.
 
-For more details, refer to the [copa design](./design.md) documentation.
+For more details, refer to the [copa design](./design.md) documentation.

website/versioned_docs/version-v0.2.x/introduction.md

@@ -36,10 +36,11 @@ This approach is motivated by the core principles of making direct container pat
 
 - **Copa supports patching _existing_ container images**.
   - Devs don't need to build their images using specific tools or modify them in some way just to support container patching.
+- **Copa supports containers without package managers _including_ distroless containers**
 - **Copa works with the existing vulnerability scanning and mitigation ecosystems**.
   - Image publishers don't need to create new workflows for container patching since Copa supports patching container images using the security update packages already being published today.
   - Consumers do not need to migrate to a new and potentially more limited support ecosystem for custom distros or change their container vulnerability scanning pipelines to include remediation, since Copa can be integrated seamlessly as an extra step to patch containers based on those scanning reports.
 - **Copa reduces the technical expertise needed and waiting on dependencies needed to patch an image**.
   - For OS package vulnerabilities, no specialized knowledge about a specific image is needed to be patch it as Copa relies on the vulnerability remediation knowledge already embedded in the reports produced by popular container scanning tools today.
 
-For more details, refer to the [copa design](./design.md) documentation.
+For more details, refer to the [copa design](./design.md) documentation.

website/versioned_docs/version-v0.3.x/introduction.md

@@ -36,10 +36,11 @@ This approach is motivated by the core principles of making direct container pat
 
 - **Copa supports patching _existing_ container images**.
   - Devs don't need to build their images using specific tools or modify them in some way just to support container patching.
+- **Copa supports containers without package managers _including_ distroless containers**
 - **Copa works with the existing vulnerability scanning and mitigation ecosystems**.
   - Image publishers don't need to create new workflows for container patching since Copa supports patching container images using the security update packages already being published today.
   - Consumers do not need to migrate to a new and potentially more limited support ecosystem for custom distros or change their container vulnerability scanning pipelines to include remediation, since Copa can be integrated seamlessly as an extra step to patch containers based on those scanning reports.
 - **Copa reduces the technical expertise needed and waiting on dependencies needed to patch an image**.
   - For OS package vulnerabilities, no specialized knowledge about a specific image is needed to be patch it as Copa relies on the vulnerability remediation knowledge already embedded in the reports produced by popular container scanning tools today.
 
-For more details, refer to the [copa design](./design.md) documentation.
+For more details, refer to the [copa design](./design.md) documentation.

website/versioned_docs/version-v0.4.x/introduction.md

@@ -36,10 +36,11 @@ This approach is motivated by the core principles of making direct container pat
 
 - **Copa supports patching _existing_ container images**.
   - Devs don't need to build their images using specific tools or modify them in some way just to support container patching.
+- **Copa supports containers without package managers _including_ distroless containers**
 - **Copa works with the existing vulnerability scanning and mitigation ecosystems**.
   - Image publishers don't need to create new workflows for container patching since Copa supports patching container images using the security update packages already being published today.
   - Consumers do not need to migrate to a new and potentially more limited support ecosystem for custom distros or change their container vulnerability scanning pipelines to include remediation, since Copa can be integrated seamlessly as an extra step to patch containers based on those scanning reports.
 - **Copa reduces the technical expertise needed and waiting on dependencies needed to patch an image**.
   - For OS package vulnerabilities, no specialized knowledge about a specific image is needed to be patch it as Copa relies on the vulnerability remediation knowledge already embedded in the reports produced by popular container scanning tools today.
 
-For more details, refer to the [copa design](./design.md) documentation.
+For more details, refer to the [copa design](./design.md) documentation.

website/versioned_docs/version-v0.5.x/introduction.md

@@ -36,10 +36,11 @@ This approach is motivated by the core principles of making direct container pat
 
 - **Copa supports patching _existing_ container images**.
   - Devs don't need to build their images using specific tools or modify them in some way just to support container patching.
+- **Copa supports containers without package managers _including_ distroless containers**
 - **Copa works with the existing vulnerability scanning and mitigation ecosystems**.
   - Image publishers don't need to create new workflows for container patching since Copa supports patching container images using the security update packages already being published today.
   - Consumers do not need to migrate to a new and potentially more limited support ecosystem for custom distros or change their container vulnerability scanning pipelines to include remediation, since Copa can be integrated seamlessly as an extra step to patch containers based on those scanning reports.
 - **Copa reduces the technical expertise needed and waiting on dependencies needed to patch an image**.
   - For OS package vulnerabilities, no specialized knowledge about a specific image is needed to be patch it as Copa relies on the vulnerability remediation knowledge already embedded in the reports produced by popular container scanning tools today.
 
-For more details, refer to the [copa design](./design.md) documentation.
+For more details, refer to the [copa design](./design.md) documentation.

website/versioned_docs/version-v0.6.x/introduction.md

@@ -36,10 +36,11 @@ This approach is motivated by the core principles of making direct container pat
 
 - **Copa supports patching _existing_ container images**.
   - Devs don't need to build their images using specific tools or modify them in some way just to support container patching.
+- **Copa supports containers without package managers _including_ distroless containers**
 - **Copa works with the existing vulnerability scanning and mitigation ecosystems**.
   - Image publishers don't need to create new workflows for container patching since Copa supports patching container images using the security update packages already being published today.
   - Consumers do not need to migrate to a new and potentially more limited support ecosystem for custom distros or change their container vulnerability scanning pipelines to include remediation, since Copa can be integrated seamlessly as an extra step to patch containers based on those scanning reports.
 - **Copa reduces the technical expertise needed and waiting on dependencies needed to patch an image**.
   - For OS package vulnerabilities, no specialized knowledge about a specific image is needed to be patch it as Copa relies on the vulnerability remediation knowledge already embedded in the reports produced by popular container scanning tools today.
 
-For more details, refer to the [copa design](./design.md) documentation.
+For more details, refer to the [copa design](./design.md) documentation.