Use overlayfs on system that supports it for cached runner #29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.