search

blackducksoftware / blackduck-docker-inspector

Apache License 2.0
20 stars 12 forks source link

9.4.3 doesn't scan, telling there is no API token #35

Closed HNKNTA closed 2 years ago

HNKNTA commented 2 years ago

Hello,

The previous version worked as expected, now we see this: 2022-04-12 06:49:27.584 ERROR 2317 --- [ main] c.s.i.b.dockerinspector.DockerInspector : Error inspecting image: Must be configured to use an API Token or username/password.

The run command with args: bash ./blackduck-docker-inspector.sh --blackduck.url=https://****.com/ --blackduck.api.token=**** --blackduck.project.name=*** --blackduck.project.version=docker_development --blackduck.codelocation.prefix=docker_development --logging.level.com.synopsys=INFO --docker.image=*** --cleanup.working.dir=false --output.include.containerfilesystem=true --output.path=./output

mprzygrodzki commented 2 years ago

Same problem here, scanning stopped to work on my side also. 

2022-04-19 21:29:40.688  WARN 85104 --- [           main] c.s.i.b.dockerinspector.DockerInspector  : *** Support for running Docker Inspector as a standalone utility is being dropped.  In the future, users should run Docker Inspector via Detect. ***
2022-04-19 21:29:40.691  INFO 85104 --- [           main] c.s.i.b.dockerinspector.DockerInspector  : Black Duck Docker Inspector 9.4.3
2022-04-19 21:29:41.406  INFO 85104 --- [           main] c.s.i.b.dockerinspector.DockerInspector  : Inspecting image:tag xxxx/zzzz:yyyy (platform: )
2022-04-19 21:29:41.408 ERROR 85104 --- [           main] c.s.i.b.dockerinspector.DockerInspector  : Error inspecting image: Must be configured to use an API Token or username/password.
2022-04-19 21:29:41.443  INFO 85104 --- [           main] c.s.i.b.dockerinspector.DockerInspector  : Returning -1
alvarospunk commented 2 years ago

I am also having this issue when calling the Docker inspection script from Jenkins, with the code inspection, it's working well.

stevebillings commented 2 years ago

The next version of Docker Inspector will not support running Docker Inspector standalone; you'll only be able to invoke Docker Inspector from Detect (which does not have this problem). My suggestion is to make that change now (invoke Docker Inspector from Detect).