How do you cache runtimes?

[dongho-jung]

I had been caching runtimes like Python, Node with the VolumeMount from local directory of host.

However, after applying cluster autoscaling, I couldn't do that anymore. Because the host itself was reset whenever it scales in/out.

So I thought can I make use of EBS volume for central cache or something like that.

yet, I'm not sure I'm doing it right. Is there anyone who tried this?

[ellisvalentiner]

We use a custom image for our runners with common tools pre-installed. It would probably be better to use a volume, but it wasn't clear to me from the docs the best way to do this and we haven't had time to dig into it.

[swanderley]

Hi @ellisvalentiner , do you mind sharing how you built your runners custom images? I'm trying to build a custom runner image with common tools for my environment but got no luck. The image is being pulled successfully but the container doesn't start, if you could share any info about how you did it, that would be much appreciated. Thank you!

[ellisvalentiner]

@swanderley The Dockerfile looks like this:

FROM summerwind/actions-runner:v2.301.1-ubuntu-20.04-6da1cde

USER runner

ENV AGENT_TOOLSDIRECTORY=/opt/hostedtoolcache
ENV DEBIAN_FRONTEND=noninteractive

# Install Python 3.9
RUN workdir=`mktemp -d` \
  && curl -L "https://github.com/actions/python-versions/releases/download/3.9.16-3647595251/python-3.9.16-linux-20.04-x64.tar.gz" -o "${workdir}/python.tar.gz" \
  && cd $workdir \
  && tar -xvzf python.tar.gz \
  && bash ./setup.sh \
  && /opt/hostedtoolcache/Python/3.9.16/x64/bin/python3 --version \
  && cd /tmp/ \
  && rm -rf $workdir

[swanderley]

Thanks @ellisvalentiner , my docker file is also building from FROM summerwind/actions-runner:v2.301.1-ubuntu-20.04-6da1cde and I'm only installing AWS CLI, for some reason the pod is able to pull the image without issues but then fails, did you see this issue when building your custom image?

here are the pod logs:
runner:
Container ID: containerd://5539f3a2ea88cb4445ec2f56b95f472132abb176740a13702580cc8334f52f80
Image: public.ecr.aws/s1b5c0g9/ecr-test:test3
Image ID: public.ecr.aws/s1b5c0g9/ecr-test@sha256:1601e5985b10e033a92cc6805c31d503feb23a8241dd00201b96ec559c224068
Port:
Host Port:
State: Terminated
Reason: Error
Exit Code: 1
Started: Thu, 26 Jan 2023 23:28:04 +0000
Finished: Thu, 26 Jan 2023 23:28:04 +0000
Ready: False

Events:
Type Reason Age From Message

Normal Scheduled 15s default-scheduler Successfully assigned default/eks-test-qhx5d-xmjb4 to ip-10-0-26-251.ec2.internal
Normal Pulling 14s kubelet Pulling image "public.ecr.aws/s1b5c0g9/ecr-test:test3"
Normal Pulled 14s kubelet Successfully pulled image "public.ecr.aws/s1b5c0g9/ecr-test:test3" in 115.714203ms
Normal Created 14s kubelet Created container runner
Normal Started 14s kubelet Started container runner
Normal Created 14s kubelet Created container docker
Normal Started 14s kubelet Started container docker
Normal Killing 12s kubelet Stopping container docker

I'll keep digging. Thanks!

[ellisvalentiner]

@swanderley can you post your Dockerfile?

[swanderley]

I got it working now, building the image with the flag --platform linux/amd64 fixed it.
Appreciate your help @ellisvalentiner . Cheers!

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬