You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the instructions in the "software security supply chain compliance" how-to guide, ran into an issue where the chalked docker builds were not including the sbom data.
Impact
All chalked docker builds that we want to have sboms embedded will not work at all.
Steps to Reproduce
ensure you have a chalk binary with the default config loaded
run ./chalk load ./configs/compliance_docker.c4m and ./chalk load ./configs/embed_sboms.c4m
check that sboms are enabled by running chalk on some binary, ex: a copy of ls
a) cp /bin/ls ./ls-test
b) ./chalk insert ls-test
c) ./chalk extract ls-test, then checking that the output written to the default ~/.local/chalk/chalk.log has the following:
Alternatively, you can run the container and manually check the chalk.json inside, which will also not have it.
Other Information
Digging into the chalk code, it looks like template toolBase in src/plugins/externalTools.nim has a loop over chalkConfig.tools. For chalking binaries, this chalkConfig.tools contains the syft tool, however when chalking docker containers, this chalkConfig.tools is always empty. This might be a bug in the underlying con4m library.
The text was updated successfully, but these errors were encountered:
Description
Following the instructions in the "software security supply chain compliance" how-to guide, ran into an issue where the chalked docker builds were not including the sbom data.
Impact
All chalked docker builds that we want to have sboms embedded will not work at all.
Steps to Reproduce
./chalk load ./configs/compliance_docker.c4m
and./chalk load ./configs/embed_sboms.c4m
a)
cp /bin/ls ./ls-test
b)
./chalk insert ls-test
c)
./chalk extract ls-test
, then checking that the output written to the default~/.local/chalk/chalk.log
has the following:./chalk docker build -t xxx -f ./tests/data/dockerfiles/valid/sample_1/Docke rfile ./tests/data/dockerfiles/valid/sample_1
./chalk extract xxx
and observe no sbom in the log file:Alternatively, you can run the container and manually check the
chalk.json
inside, which will also not have it.Other Information
Digging into the chalk code, it looks like
template toolBase
insrc/plugins/externalTools.nim
has a loop overchalkConfig.tools
. For chalking binaries, thischalkConfig.tools
contains thesyft
tool, however when chalking docker containers, thischalkConfig.tools
is always empty. This might be a bug in the underlying con4m library.The text was updated successfully, but these errors were encountered: