Cache key not found in GCP cloud run self-hosted runner #1465
Unanswered
simon-doss
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am trying to use self hosted runners on GCP cloud run to reduce build costs, but I am running into an issue where
actions/cache/restore@v4
doesn't seem to be finding the cache key. However, the cache key is found when I am using Github-hosted runners. I'm able to access Github API from the cloud run container because I am able to create and delete runners from the container. Is there anything else I need to do to get the cache key to get found?I checked the restore keys and paths are the same when I am saving and restoring. To my understanding, the cache is shared and hosted on Github's infrastructure, so it shouldn't matter where the runner is hosted as long as it has access to Github's network.
Beta Was this translation helpful? Give feedback.
All reactions