-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support input as tarball(s) and VM images in root fileystem pipelines #96
Comments
pombredanne
changed the title
Support input as tarball(s) in root fileystem pipelines
Support input as tarball(s) and VM images in root fileystem pipelines
Feb 13, 2021
tdruez
added a commit
that referenced
this issue
Feb 15, 2021
- Improve support for unknown distros in docker and root_filesystem pipelines #97 Signed-off-by: Thomas Druez <[email protected]>
Support added in eb970db |
Tarballs are now supported by the root_filesystems pipeline. Also, the command line can be used as follow:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To run a root_filesystem pipeline, we need to do this for now:
(thanks to @JonoYang for providing the steps! )
Start from a new project:
scanpipe create-project myproj
scancode.io/var/projects/<myproj-id>/codebase
. This directory should look like a rootfs.scanpipe add-pipeline --project myproj scanpipe/pipelines/root_filesystems.py
scanpipe run --project myproj
This is not a great UX. We should support having an input as a tarball or as an image (see aboutcode-org/extractcode#16 )
In doing so there is some minor issue to resolve which is to determine where is the root of a rootfs.
/usr/lib
,/bin
,/etc
, ... etc.)The text was updated successfully, but these errors were encountered: