Skip to content

Fix syft output folder permissions #343

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

Closed
wants to merge 3 commits into from
Closed

Conversation

thespad
Copy link
Member

@thespad thespad commented Jun 9, 2025

linuxserver.io


  • I have read the contributing guideline and understand that I have made the correct modifications

Description:

Syft 1.27.0 "Harden[s] Container Runtime with Non-Root User", specifically 65532, this breaks our current output as we use mktemp, which creates the folder as the user that runs it. This means we now need to chown the mktemp'd folder so that Syft has permissions to write to it.

Benefits of this PR and context:

How Has This Been Tested?

Source / References:

@thespad thespad requested a review from a team June 9, 2025 20:41
@thespad thespad self-assigned this Jun 9, 2025
@LinuxServer-CI LinuxServer-CI moved this to PRs Ready For Team Review in Issue & PR Tracker Jun 9, 2025
@thespad thespad changed the title pin to specific syft version (#342) Fix syft output folder permissions Jun 9, 2025
@github-project-automation github-project-automation bot moved this from PRs Ready For Team Review to PRs Approved in Issue & PR Tracker Jun 10, 2025
@LinuxServer-CI
Copy link
Contributor

This pull request has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

@thespad
Copy link
Member Author

thespad commented Jul 13, 2025

Don't think this is going to be needed because Syft have changed their approach upstream

@thespad thespad closed this Jul 13, 2025
@LinuxServer-CI LinuxServer-CI moved this from PRs to Done in Issue & PR Tracker Jul 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

4 participants