-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
claircore: open /tmp: operation not supported #2009
Comments
Clair 4.7.3 and later require wherever it's configured to write temporary files to support the O_TMPFILE open(2) flag. This has been in the kernel and most in-tree filesystems for over a decade. What filesystem is mounted at $TMPDIR (or /tmp if that's unset)? |
Its xfs filesystem. It has been mounted to an attached block volume. /random/tmp /tmp xfs bind,defaults,noatime,_netdev 0 2 where |
Workaround for issue quay#2009 suggested in docker/compose#1339 (comment)
Workaround for issue quay#2009 suggested in docker/compose#1339 (comment) Signed-off-by: perat <[email protected]>
Is the dependency on that mount expressed in the service manager? |
yes, the above entries are in /etc/fstab |
We checked in logs that open with O_TMPFILE fails. [~] docksh clairv4 Is it possible to place the fix where fall back happens to a non-O_TMPFILE path if the open() fails. |
Also, from logs the permissions are 0644, will increasing the permissions help? openat(AT_FDCWD, "/tmp", O_WRONLY|O_CLOEXEC|O_TMPFILE, 0644 |
I believe it should move under quay/claircore , there is similar PR quay/claircore#1140 Struggling with same, tmpfs in our cluster and nfsfs for pvc do not support this operation. Can there be a patch in clair core similarly to this? |
fixed with quay/claircore#1292 , waiting for merge and release of #2020 |
This was completed a while ago, closing |
Description of Problem / Feature Request
We are running Clair in Combo mode. It is running fine with version 4.7.1, but when we upgraded to 4.7.3, getting the 500 internal server error.
Expected Outcome
Scan should run successfully, currently it is failing with 500 internal server error.
Actual Outcome
he scan is failing with 500 internal server error.
2024-03-14T08:58:52Z DBG index error error="unexpected return status: 500" digest=sha256:xxxxxxxxxx ref=/postgres:12.1
2024-03-14T08:58:52Z ERR error="unexpected return status: 500"
Environment
uname -a
): 5.4.17-2136.304.4.1.el7uek.x86_64kubectl version
): Docker Version: 19.03.11-olThe text was updated successfully, but these errors were encountered: