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

ramdisk buildbot worker draft #133

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

Conversation

Akira25
Copy link
Member

@Akira25 Akira25 commented Oct 16, 2024

Adds flag to define, wether a builodbot worker should hava a ramdisk or not

@Akira25 Akira25 force-pushed the add_ramdisk_worker_perry branch from 2badbf1 to 02c7944 Compare October 16, 2024 13:40
@pktpls
Copy link
Contributor

pktpls commented Oct 18, 2024

I like this - what's missing?

Btw an alternative way to do a ramdisk is to run Podman in targets.py and packages.py with --tmpfs /root:rw,size=6291456k,mode=1777, where the worker itself is persistent, but the build is done in a ramdisk.

@pktpls
Copy link
Contributor

pktpls commented Oct 18, 2024

(I picked 76e4d79 to main)

@Akira25
Copy link
Member Author

Akira25 commented Oct 20, 2024

I like this - what's missing?

The persistance of the installation at the ramdisk is included, but not entirely finished yet. Needs to be tested.

Btw an alternative way to do a ramdisk is to run Podman in targets.py and packages.py with --tmpfs /root:rw,size=6291456k,mode=1777, where the worker itself is persistent, but the build is done in a ramdisk.

If you like too, alter the MR in that way. Sounds also a bit more smooth and precise to me, than reconfiguring podman entirely.

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.

2 participants