-
I'm running the current GitHub Action Runner (v2.317.0) on the current Bottlerocket (Bottlerocket OS 1.20.2 (aws-k8s-1.29)), with Docker-in-Docker. Often it works, although there are some warnings about networking Click for details
It can take less than a second for Docker to start. In the example above it took 45 seconds. I am allocating 2250m of CPU (over 2 full CPUs) and 6GiB of memory to the pod, so if it is a resource issue, it would have to be a system resource issue. Does running Docker in Docker from a privileged Pod put pressure on the system? Given that the Pod is just sleeping, that should leave 2 CPUs available for the system to get Docker running. I suppose I should point out that I'm launching 90 pods all at once onto a I have worked around the issue for now by extending the timeout from 120 seconds to 300 seconds, but that is kind of ridiculous. I would really like to find out what the issue is and get it fixed. I'm asking here because this is all running on Bottlerocket and I don't know where to look. I'm pretty disoriented compared to Amazon Linux. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
It appears this is due to disk I/O saturation, due to 50 Pods launching at once on this 196 vCPU instance, backed by a single normal |
Beta Was this translation helpful? Give feedback.
It appears this is due to disk I/O saturation, due to 50 Pods launching at once on this 196 vCPU instance, backed by a single normal
gp3
EBS volume, and not a problem specific to Bottlerocket. My apologies.