Skip to content

Commit

Permalink
Do not use effect.NewExecutor use CommandExecutor instead
Browse files Browse the repository at this point in the history
When running `syft`, do not use effect.NewExecutor which runs the command with a tty. This seems to cause an issue with syft (or possibly with our tty library pty), and in either case you end up with stray formatting characters even though we tell syft to be quiet. Using CommandExecutor is basically the same, but it doesn't run with a tty.

Signed-off-by: Daniel Mikusa <[email protected]>
  • Loading branch information
dmikusa committed Oct 4, 2024
1 parent 1c610b5 commit 511761b
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion native/build.go
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@ func (b Build) Build(context libcnb.BuildContext) (libcnb.BuildResult, error) {
)

if b.SBOMScanner == nil {
b.SBOMScanner = sbom.NewSyftCLISBOMScanner(context.Layers, effect.NewExecutor(), b.Logger)
b.SBOMScanner = sbom.NewSyftCLISBOMScanner(context.Layers, effect.CommandExecutor{}, b.Logger)
}
if err := b.SBOMScanner.ScanLaunch(context.Application.Path, libcnb.SyftJSON, libcnb.CycloneDXJSON); err != nil {
return libcnb.BuildResult{}, fmt.Errorf("unable to create Build SBoM \n%w", err)
Expand Down

0 comments on commit 511761b

Please sign in to comment.