pivotal / LicenseFinder

Find licenses for your project's dependencies.
MIT License
1.73k stars 340 forks source link

license_finder: command not found #707

Open boev opened 4 years ago

boev commented 4 years ago

Hello,

Using the official docker image into our CI/CD pipeline gives the following error. Do I need to install license_finder or symlink anything for the command to work. Am I using it wrong?

Image: licensefinder/license_finder:6.1.0 Error: $ license_finder action_items /bin/bash: line 144: license_finder: command not found ERROR: Job failed: exit code 1

Thank you for your time and support.

cf-gitbot commented 4 years ago

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

xtreme-shane-lattanzio commented 4 years ago

@boev Are you running in a subshell? In general to login and run in the license finder docker we use a command like docker run -v ~/workspace/:/workspace/ -it licensefinder/license_finder bin/bash --login'

faraonc commented 4 years ago

I was wondering the need for running /bin/bash -l. This can be problematic if volume mount is not supported for the CI. Normally, you would have a container with the binaries needed to run against a repository.

TobiTh commented 2 years ago

Is there a workaround for using bash -l? It does break in our CI with the following error mesg: ttyname failed: Inappropriate ioctl for device. Manual sourcing instead of using the --login option does not work either.

tpiecora commented 1 year ago

I'm also looking for a workaround. I have a different use case where I have created a wrapper around the LicenseFinder docker image so I can generate reports on demand, however this is proving difficult with the need for bash login. It appears that environment configuration needed to run license_finder is loaded into the environment when you login, though I haven't identified what configuration it specifically needed yet. Ideally I could set this configuration on the container and not login.

Any insight here would be greatly appreciated.