Skip to content
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

Set umask in container #480

Merged
merged 1 commit into from
May 24, 2024
Merged

Set umask in container #480

merged 1 commit into from
May 24, 2024

Conversation

joeshannon
Copy link
Contributor

Performing an editable install on a shared filesystem scratch area causes cache/version files to be written in the source repository.

With the container's default umask of 0022 the files are not group writable which can lead to frustration when attempting to clean up the scratch area.

Use the DLS "standard" of 0002.

Additionally modify the looping to only pickup directories within the scratch area.

Fixes #478.

Copy link

codecov bot commented May 21, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.06%. Comparing base (a3f023f) to head (503583f).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #480   +/-   ##
=======================================
  Coverage   91.06%   91.06%           
=======================================
  Files          40       40           
  Lines        1667     1667           
=======================================
  Hits         1518     1518           
  Misses        149      149           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@joeshannon joeshannon force-pushed the 478-set-umask-in-container branch 2 times, most recently from e64c70f to 77c2373 Compare May 21, 2024 16:03
@joeshannon
Copy link
Contributor Author

Would it help to additionally add a pip freezehere at the end to be clear about what we have installed?

@callumforrester
Copy link
Contributor

Unsure, should be a separate PR if so

Performing an editable install on a shared filesystem scratch area
causes cache/version files to be written in the source repository.

With the container's default umask of 0022 the files are not group
writable which can lead to frustration when attempting to clean up the
scratch area.

Use the DLS "standard" of 0002.

Additionally modify the looping to only pickup directories within the
scratch area.

Fixes #478.
@callumforrester callumforrester force-pushed the 478-set-umask-in-container branch from 77c2373 to 503583f Compare May 24, 2024 07:44
Copy link
Contributor

@DiamondJoseph DiamondJoseph left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be an option in the python-copier-template?

@callumforrester
Copy link
Contributor

That's a question for @coretl and @GDYendell

@DiamondJoseph
Copy link
Contributor

I'll make an issue and discussion can take place there

@joeshannon joeshannon merged commit 6f08f68 into main May 24, 2024
23 of 24 checks passed
@joeshannon joeshannon deleted the 478-set-umask-in-container branch May 24, 2024 14:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Mitigate permission issues in scratch area
3 participants