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

Use overlayfs on system that supports it for cached runner #29

Merged
merged 1 commit into from
Jul 30, 2024

Conversation

gabriel-samfira
Copy link
Member

@gabriel-samfira gabriel-samfira commented Jul 4, 2024

This change allows providers to use overlayfs for the cached runner, with a fallback to the old way of copying everything.

The writable upper dir is customizable via extra specs by setting the extra_context["OVF_DIR"] value to a different location on disk.

Example:

garm-cli pool update 84944b12-5f80-469c-9152-4e352ea570f8 
  --extra-specs='{"extra_context": {"OFS_DIR": "/home/runner/overlay-work"}}'

If your runner has a volume attached that you'd rather use for the overlay data, or just because you prefer a different location on disk, this option should give you the desired result. If not set, it falls back to /opt/work

This should speed up runner installation considerably.

Providers will have to be updated and the extra_context extra spec to be added to the allowed extra specs of the provider before this works.

@gabriel-samfira
Copy link
Member Author

CC @maigl @bavarianbidi

@gabriel-samfira
Copy link
Member Author

CC @Hdom

@gabriel-samfira gabriel-samfira merged commit 186120d into cloudbase:main Jul 30, 2024
2 checks passed
@gabriel-samfira gabriel-samfira deleted the use-overlayfs branch July 30, 2024 16:02
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.

1 participant