[Workload]. Reduce the amount of clutter in your image

[wvwatson]

Title: [Workload] microservices test: uncluttered_image

Is your workload test idea related to a problem? Please describe.

• Some images have inappropriate data and binaries installed on them

Describe the solution you'd like

• inappropriate binaries to search for: e.g. netstat, nmap
• Size reduction: To reduce the size of your image, install only what is strictly needed inside it. It might be tempting to install extra packages, and then remove them at a later step. However, this approach isn't sufficient. Because each instruction of the Dockerfile creates a layer, removing data from the image in a later step than the step that created it doesn't reduce the size of the overall image (the data is still there, just hidden in a deeper layer). https://cloud.google.com/architecture/best-practices-for-building-containers#reduce_the_amount_of_clutter_in_your_image

Test Category Name

• Microservices

---

Documentation tasks:

• Update installation instructions if needed
• Update Test Categories md if needed
• Update USAGE md if needed
  • How to run
  • Description and details
    • What the best practice is
    • Why are we testing this
  • Remediation steps if test does not pass

QA tasks

Dev Review:

• walk through A/C
• do you get the expected result?
• if yes,
  • move to Needs Peer Review column
  • create Pull Request and follow check list
  • Assign 1 or more people for peer review
• if no, document what additional tasks will be needed

Peer review:

• walk through A/C
• do you get the expected result?
• if yes,
  • move to Reviewer Approved column
  • Approve pull request
• if no,
  • document what did not go as expected, including error messages and screenshots (if possible)
  • Add comment to pull request
  • request changes to pull request

[HashNuke]

I just tried dive to identify container image inefficiency across the image layers. This identifies files that are added and removed across layers of a container image. Tried it with the envoy container image.

But the issues page of the project has some hints about not supporting new container formats, project not maintained, etc

[lixuna]

@taylor is this issue still relevant for CNTI?