User feedback has shown that there are times when system minimum requirements are not met and actions like lockfile generation failed, but with less than helpful output such that the source of the problem and possible corrective actions were not provided. Here is one example of such output:
---TRIMMED---
Caused by:
0: Lockfile generation failed! For details, see: https://docs.phylum.io/docs/lockfile_generation
1: subprocess failed:
❗ Error: input/output error: Function not implemented (os error 38)
In this case, the Error message was confusing and the provided link did not yield any more detail to resolve the error. It turned out to be the case that the system kernel version was too old to support one of the required/requested sandbox permissions, but that was only uncovered by developers of the tool after reaching out for their support. The user had no clue what was wrong or what they could do themselves to figure that out.
This issue is meant to help users in as many ways as possible. Actions which may help include, but are not limited to:
Put clear prerequisite minimums (kernel, glibc, etc) in the appropriate doc locations (CLI? birdcage?)
Update installers to check for the prerequisites and fail with helpful messages when they aren't met
Update error messages to provide more hints as to the source of the failure and/or links to resources that can provide more detail
Acceptance Criteria
[ ] Documentation is updated to minimally specify the sources of system pre-requisites and why/when certain actions may not work when those aren't met
[x] Error output is improved to provide more detail and/or actionable next steps
Overview
User feedback has shown that there are times when system minimum requirements are not met and actions like lockfile generation failed, but with less than helpful output such that the source of the problem and possible corrective actions were not provided. Here is one example of such output:
In this case, the
Errormessage was confusing and the provided link did not yield any more detail to resolve the error. It turned out to be the case that the system kernel version was too old to support one of the required/requested sandbox permissions, but that was only uncovered by developers of the tool after reaching out for their support. The user had no clue what was wrong or what they could do themselves to figure that out.This issue is meant to help users in as many ways as possible. Actions which may help include, but are not limited to:
Acceptance Criteria