Run clair as a binary

[chakradharv]

Hi. How do I run Clair as binary fine without the docker? I have a requirement to run Clair as binary file. I can setup my own postgres. Could you please help with this?

[hdonnay]

Building and running the binary should be fine. It's configured identically: set the flags or environment variables to indicate the mode and the config file.

[cvangeti]

@hdonnay could you please help me with this?

[cvangeti]

Also, I am getting this error for the centos:7 image

./clairctl report centos:7
2021/04/15 11:50:05 indexer error: failed to scan all layer contents: rpm: failed to untar: exit status 1

[hdonnay]

It looks like you have a trailing newline on the uri field, which almost certainly shouldn't be there.

An indexer error indicates something went wrong in the indexing process. The clair logs should have more information; that error reports something wrong when attempting to run tar, my guess would be an invalid input or perhaps a tar that doesn't understand the arguments clair is using.

[jovandeginste]

An indexer error indicates something went wrong in the indexing process. The clair logs should have more information; that error reports something wrong when attempting to run tar, my guess would be an invalid input or perhaps a tar that doesn't understand the arguments clair is using.

Correct; this is the full error (from the logs); seems like --delay-directory-restore is the issue...

rpm/Scanner.Scan,
kind:package,
layer:sha256:...,
scanner:rpm,
state:CheckManifest,
version:v0.0.2,
dir:/tmp/rpmscanner.870006625,
cmd:[
tar,-xC,/tmp/rpmscanner.870006625,--exclude,dev,--exclude,.wh*,--delay-directory-restore
],
stderr:tar: unrecognized option: delay-directory-restore
BusyBox v1.32.1 () multi-call binary.

Usage: tar c|x|t [-ZzJjahmvokO] [-f TARFILE] [-C DIR] [-T FILE] [-X FILE] [--exclude PATTERN]... [FILE]...

Create, extract, or list files from a tar file

	c	Create
	x	Extract
	t	List
	-f FILE	Name of TARFILE ('-' for stdin/out)
	-C DIR	Change to DIR before operation
	-v	Verbose
	-O	Extract to stdout
	-m	Don't restore mtime
	-o	Don't restore user:group
	-k	Don't replace existing files
	-Z	(De)compress using compress
	-z	(De)compress using gzip
	-J	(De)compress using xz
	-j	(De)compress using bzip2
	-a	(De)compress based on extension
	-h	Follow symlinks
	-T FILE	File with names to include
	-X FILE	File with glob patterns to exclude
	--exclude PATTERN	Glob pattern to exclude

[jovandeginste]

Apologies; above error was because I built my own container. The official container (v4.1.2) gives this error:

{
  "level": "error",
  "component": "rpm/Scanner.Scan",
  "kind": "package",
  "layer": "sha256:...",
  "manifest": "sha256:...",
  "scanner": "rpm",
  "state": "CheckManifest",
  "version": "v0.0.2",
  "dir": "/tmp/rpmscanner.679648756",
  "cmd": [
    "tar",
    "--extract",
    "--exclude",
    "dev",
    "--exclude",
    ".wh*",
    "--delay-directory-restore",
    "--no-same-owner",
    "--no-same-permissions"
  ],
  "stderr": "",
  "err": "signal: killed",
  "time": "2021-08-11T08:40:11Z",
  "message": "error extracting layer"
}

{
  "level": "error",
  "component": "internal/indexer/controller/Controller.Index",
  "manifest": "sha256:...",
  "state": "CheckManifest",
  "error": "failed to scan all layer contents: zip error: zip: not a valid zip file",
  "time": "2021-08-11T08:40:11Z",
  "message": "error during scan"
}

[jovandeginste]

Just saw v4.2.0 was released, tested with that image, and having success now.

[crozzy]

Thanks for the update @jovandeginste, any chance you could share (non-sensitive) information about the image/manifest you are scanning.

[jovandeginste]

It was based on an old (centos6) image; legacy app...

[hdonnay]

I think that error is also quay/claircore#434