3 Answers
- Newest
- Most votes
- Most comments
3
Hlo,
Please follow below Documents,
[https://repost.aws/knowledge-center/eks-failed-create-pod-sandbox]
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.
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.
Relevant content
- asked 15 days ago
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 5 months 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