Closed ackava closed 2 months ago
This is because Docker Scout is creating an SBOM for your images, which can be resource intensive. You can update your build process to include the creation of an SBOM which Docker Scout will be able to read as part of the indexing process. You can set your build process to generate this with --sbom=1 --provenance=1
(on the CLI), and by using buildx build
.
Having SBOMs is good software supply chain practice, but if you don't create your own SBOMs, and don't want Docker Scout to generate these retrospectively, you can turn off this option In Docker Desktop, Settings > General settings > deselect SBOM indexing
Thank you.
On dev machines, building new image has become extremely slow due to Docker Scout utilizing full CPU, I totally understand the purpose of Docker Scout, but there should be some way to turn it off completely while developing and testing new containers. Current workaround is to use remote Linux VM instead of Docker Desktop on our own machine to build new images.