EKS creating pod stuck at pulling image

0

Hello everyone,

I am using EKS with Kubernetes version 1.29, worker node version 1.28

Pods take a very long time to be created, about 1 hour for image size 1.33 GB (private ghcr.io registry)

When I describe the pod, events are normal, it is stuck at pulling image without any error.

sample: Normal Pulling 51m kubelet Pulling image "ghcr.io/aura-nw/long-campaign-be:euphoria_6cf3d53"

Create a docker-in-docker pod in that cluster and pull the same image to test, it only took about 4 minutes.

Please help if you know anything about this case. Thanks!

Kien
asked 20 days ago622 views
3 Answers
3
EXPERT
answered 20 days ago
profile picture
EXPERT
reviewed 20 days ago
profile picture
EXPERT
A_J
reviewed 20 days ago
  • thank you but nothing helpful from the docs, don't have any error, just pulling process takes very long time but still succeed at the end

2

Hello,

To address the issue

Check Image Pull Secrets:

  • Ensure you have configured imagePullSecrets correctly in your pod specification to authenticate with the private ghcr.io registry.
apiVersion: v1
kind: Pod
metadata:
  name: your-pod-name
spec:
  containers:
  - name: your-container-name
    image: ghcr.io/aura-nw/long-campaign-be:euphoria_6cf3d53
  imagePullSecrets:
  - name: your-secret-name

Create a secret with your GitHub Container Registry credentials:

kubectl create secret docker-registry your-secret-name \
  --docker-server=ghcr.io \
  --docker-username=your-username \
  --docker-password=your-personal-access-token

Check Node Resources:

  • Ensure your worker nodes have sufficient resources (CPU, memory, network bandwidth) to pull the images efficiently. Insufficient resources can cause delays in pulling large images.
  • Monitor node status and resource usage:
kubectl describe nodes
  • Ensure VPC, subnets, and security groups are properly configured for internet access and efficient image pulling.

These steps should help in resolving the issue with image pulling in your EKS cluster.

profile picture
EXPERT
answered 20 days ago
profile picture
EXPERT
reviewed 20 days ago
profile picture
EXPERT
A_J
reviewed 20 days ago
  • Node Resources seem normal, can pull normally when exec and pull inside a test pod but image pulling for creating container is very slow without any error

1

Hello,

When pulling images from a private registry, use imagePullSecrets in the workload manifest to specify the credentials. These credentials authenticate with the private registry, allowing the pod to pull images from the specified private repository.

https://repost.aws/knowledge-center/eks-pod-status-errors

profile picture
EXPERT
answered 20 days ago
profile picture
EXPERT
reviewed 20 days ago
profile picture
EXPERT
A_J
reviewed 20 days ago