-
Notifications
You must be signed in to change notification settings - Fork 49
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
chore: proposal refactor #670
base: main
Are you sure you want to change the base?
Conversation
|
||
RUN --mount=type=cache,dst=/var/cache/rpm-ostree \ | ||
--mount=type=bind,from=ctx,src=/,dst=/ctx \ | ||
--mount=type=bind,rw=true,from=ctx,src=/,dst=/ctx \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why does is this bind mount changed to rw=true
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was added because I got annoyed with permissions on the scripts directory. The Containerfile now chmod +x
s all scripts in the directory, which required write access. It can be removed if we wish to proceed with this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the bind being read-only, seems a bit odd to mutate the scripts on the fly.
Alternatives are:
- chmod +x the scripts locally and commit the change
bash /ctx/build_files/scriptname.sh
at runtime instead of/ctx/build_files/scriptname.sh
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Option 2 seems solid, if all the scripts are standardized as bash scripts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I find it unlikely for us to move off of bash any time soon so option 2 would be reasonable for me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't really understand why the permissions are problematic in the first place. They are stored in git repo.
Only potential problem is someone committing in windows (not WSL).
If you aren't reliant on exit for control flow, you could source the
scripts instead
…On Tue, Nov 5, 2024, 6:53 PM Robert Sturla ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In Containerfile
<#670 (comment)>:
>
RUN --mount=type=cache,dst=/var/cache/rpm-ostree \
- --mount=type=bind,from=ctx,src=/,dst=/ctx \
+ --mount=type=bind,rw=true,from=ctx,src=/,dst=/ctx \
This was added because I got annoyed with permissions on the scripts/
directory. The Containerfile now chmod +xs all scripts in the directory,
which required write access. It can be removed if we wish to proceed with
this.
—
Reply to this email directly, view it on GitHub
<#670 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQPNFFIQXP76FLSNF2ZCZODZ7FK6PAVCNFSM6AAAAABQ7LUVHKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDIMJXGAYDENJQGI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Just an idea of a refactor to make it slightly easier to work in this repo.
TODO: