Unable to pull images in Kubernetes
Clash Royale CLAN TAG#URR8PPP
up vote
3
down vote
favorite
I am running Kubernetes on CentOS 7, and I am unable to deploy pods.ÃÂ
After running
# kubectl run nginx --image=nginx
I run
# kubectl describe pod nginx
which gives the following output:
Name: nginx-701339712-8sx7m
Namespace: default
Node: node2/192.168.1.126
Start Time: Fri, 27 Oct 2017 14:06:35 -0400
Labels: pod-template-hash=701339712
run=nginx
Status: Pending
IP:
Controllers: ReplicaSet/nginx-701339712
Containers:
nginx:
Container ID:
Image: nginx
Image ID:
Port:
State: Waiting
Reason: ContainerCreating
Ready: False
Restart Count: 0
Volume Mounts: <none>
Environment Variables: <none>
Conditions:
Type Status
Initialized True
Ready False
PodScheduled True
No volumes.
QoS Class: BestEffort
Tolerations: <none>
Events:
FirstSeen LastSeen Count From SubObjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ -------
21s 21s 1 default-scheduler Normal Scheduled Successfully assigned nginx-701339712-8sx7m to node2
21s 7s 2 kubelet node2 Warning FailedSync Error syncing pod, skipping: failed to "StartContainer" for "POD" with ErrImagePull: "image pull failed for registry.access.redhat.com/rhel7/pod-infrastructure:latest, this may be because there are no credentials on this request. details: (open /etc/docker/certs.d/registry.access.redhat.com/redhat-ca.crt: no such file or directory)"
If you scroll the last line,
youâÂÂll see that itâÂÂs going to redhat.com and failing.ÃÂ
I donâÂÂt know why itâÂÂs going to the RedHat repo for image pull;
it should pull from docker hub.
docker kubernetes
add a comment |Â
up vote
3
down vote
favorite
I am running Kubernetes on CentOS 7, and I am unable to deploy pods.ÃÂ
After running
# kubectl run nginx --image=nginx
I run
# kubectl describe pod nginx
which gives the following output:
Name: nginx-701339712-8sx7m
Namespace: default
Node: node2/192.168.1.126
Start Time: Fri, 27 Oct 2017 14:06:35 -0400
Labels: pod-template-hash=701339712
run=nginx
Status: Pending
IP:
Controllers: ReplicaSet/nginx-701339712
Containers:
nginx:
Container ID:
Image: nginx
Image ID:
Port:
State: Waiting
Reason: ContainerCreating
Ready: False
Restart Count: 0
Volume Mounts: <none>
Environment Variables: <none>
Conditions:
Type Status
Initialized True
Ready False
PodScheduled True
No volumes.
QoS Class: BestEffort
Tolerations: <none>
Events:
FirstSeen LastSeen Count From SubObjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ -------
21s 21s 1 default-scheduler Normal Scheduled Successfully assigned nginx-701339712-8sx7m to node2
21s 7s 2 kubelet node2 Warning FailedSync Error syncing pod, skipping: failed to "StartContainer" for "POD" with ErrImagePull: "image pull failed for registry.access.redhat.com/rhel7/pod-infrastructure:latest, this may be because there are no credentials on this request. details: (open /etc/docker/certs.d/registry.access.redhat.com/redhat-ca.crt: no such file or directory)"
If you scroll the last line,
youâÂÂll see that itâÂÂs going to redhat.com and failing.ÃÂ
I donâÂÂt know why itâÂÂs going to the RedHat repo for image pull;
it should pull from docker hub.
docker kubernetes
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I am running Kubernetes on CentOS 7, and I am unable to deploy pods.ÃÂ
After running
# kubectl run nginx --image=nginx
I run
# kubectl describe pod nginx
which gives the following output:
Name: nginx-701339712-8sx7m
Namespace: default
Node: node2/192.168.1.126
Start Time: Fri, 27 Oct 2017 14:06:35 -0400
Labels: pod-template-hash=701339712
run=nginx
Status: Pending
IP:
Controllers: ReplicaSet/nginx-701339712
Containers:
nginx:
Container ID:
Image: nginx
Image ID:
Port:
State: Waiting
Reason: ContainerCreating
Ready: False
Restart Count: 0
Volume Mounts: <none>
Environment Variables: <none>
Conditions:
Type Status
Initialized True
Ready False
PodScheduled True
No volumes.
QoS Class: BestEffort
Tolerations: <none>
Events:
FirstSeen LastSeen Count From SubObjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ -------
21s 21s 1 default-scheduler Normal Scheduled Successfully assigned nginx-701339712-8sx7m to node2
21s 7s 2 kubelet node2 Warning FailedSync Error syncing pod, skipping: failed to "StartContainer" for "POD" with ErrImagePull: "image pull failed for registry.access.redhat.com/rhel7/pod-infrastructure:latest, this may be because there are no credentials on this request. details: (open /etc/docker/certs.d/registry.access.redhat.com/redhat-ca.crt: no such file or directory)"
If you scroll the last line,
youâÂÂll see that itâÂÂs going to redhat.com and failing.ÃÂ
I donâÂÂt know why itâÂÂs going to the RedHat repo for image pull;
it should pull from docker hub.
docker kubernetes
I am running Kubernetes on CentOS 7, and I am unable to deploy pods.ÃÂ
After running
# kubectl run nginx --image=nginx
I run
# kubectl describe pod nginx
which gives the following output:
Name: nginx-701339712-8sx7m
Namespace: default
Node: node2/192.168.1.126
Start Time: Fri, 27 Oct 2017 14:06:35 -0400
Labels: pod-template-hash=701339712
run=nginx
Status: Pending
IP:
Controllers: ReplicaSet/nginx-701339712
Containers:
nginx:
Container ID:
Image: nginx
Image ID:
Port:
State: Waiting
Reason: ContainerCreating
Ready: False
Restart Count: 0
Volume Mounts: <none>
Environment Variables: <none>
Conditions:
Type Status
Initialized True
Ready False
PodScheduled True
No volumes.
QoS Class: BestEffort
Tolerations: <none>
Events:
FirstSeen LastSeen Count From SubObjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ -------
21s 21s 1 default-scheduler Normal Scheduled Successfully assigned nginx-701339712-8sx7m to node2
21s 7s 2 kubelet node2 Warning FailedSync Error syncing pod, skipping: failed to "StartContainer" for "POD" with ErrImagePull: "image pull failed for registry.access.redhat.com/rhel7/pod-infrastructure:latest, this may be because there are no credentials on this request. details: (open /etc/docker/certs.d/registry.access.redhat.com/redhat-ca.crt: no such file or directory)"
If you scroll the last line,
youâÂÂll see that itâÂÂs going to redhat.com and failing.ÃÂ
I donâÂÂt know why itâÂÂs going to the RedHat repo for image pull;
it should pull from docker hub.
docker kubernetes
edited Oct 27 '17 at 21:50
G-Man
11.6k82657
11.6k82657
asked Oct 27 '17 at 18:09
Mohd
146114
146114
add a comment |Â
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
1
down vote
not recommand edit /etc/kubernetes/kubelet to solve this error.
if you see image pull failed for registry.access.redhat.com/rhel7/pod-infrastructure:latest, you can try run command:
yum install -y rhsm
I solved the same error after run the command.
is it a redhat repository?
â Mohd
Nov 30 '17 at 6:31
This doesn't work when you're using centos. I had to run "yum install subscription-manager". That appeared to work.
â Matthew
Jan 17 at 14:54
add a comment |Â
up vote
0
down vote
I solved it commenting the line :
KUBELET_POD_INFRA_CONTAINER="--pod-infra-containerimage=registry.access.redhat.com/rhel7/pod-infrastructure:latest"
in /etc/kubernetes/kubelet
on each of my slaves
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
not recommand edit /etc/kubernetes/kubelet to solve this error.
if you see image pull failed for registry.access.redhat.com/rhel7/pod-infrastructure:latest, you can try run command:
yum install -y rhsm
I solved the same error after run the command.
is it a redhat repository?
â Mohd
Nov 30 '17 at 6:31
This doesn't work when you're using centos. I had to run "yum install subscription-manager". That appeared to work.
â Matthew
Jan 17 at 14:54
add a comment |Â
up vote
1
down vote
not recommand edit /etc/kubernetes/kubelet to solve this error.
if you see image pull failed for registry.access.redhat.com/rhel7/pod-infrastructure:latest, you can try run command:
yum install -y rhsm
I solved the same error after run the command.
is it a redhat repository?
â Mohd
Nov 30 '17 at 6:31
This doesn't work when you're using centos. I had to run "yum install subscription-manager". That appeared to work.
â Matthew
Jan 17 at 14:54
add a comment |Â
up vote
1
down vote
up vote
1
down vote
not recommand edit /etc/kubernetes/kubelet to solve this error.
if you see image pull failed for registry.access.redhat.com/rhel7/pod-infrastructure:latest, you can try run command:
yum install -y rhsm
I solved the same error after run the command.
not recommand edit /etc/kubernetes/kubelet to solve this error.
if you see image pull failed for registry.access.redhat.com/rhel7/pod-infrastructure:latest, you can try run command:
yum install -y rhsm
I solved the same error after run the command.
answered Nov 24 '17 at 14:22
David Liu
111
111
is it a redhat repository?
â Mohd
Nov 30 '17 at 6:31
This doesn't work when you're using centos. I had to run "yum install subscription-manager". That appeared to work.
â Matthew
Jan 17 at 14:54
add a comment |Â
is it a redhat repository?
â Mohd
Nov 30 '17 at 6:31
This doesn't work when you're using centos. I had to run "yum install subscription-manager". That appeared to work.
â Matthew
Jan 17 at 14:54
is it a redhat repository?
â Mohd
Nov 30 '17 at 6:31
is it a redhat repository?
â Mohd
Nov 30 '17 at 6:31
This doesn't work when you're using centos. I had to run "yum install subscription-manager". That appeared to work.
â Matthew
Jan 17 at 14:54
This doesn't work when you're using centos. I had to run "yum install subscription-manager". That appeared to work.
â Matthew
Jan 17 at 14:54
add a comment |Â
up vote
0
down vote
I solved it commenting the line :
KUBELET_POD_INFRA_CONTAINER="--pod-infra-containerimage=registry.access.redhat.com/rhel7/pod-infrastructure:latest"
in /etc/kubernetes/kubelet
on each of my slaves
add a comment |Â
up vote
0
down vote
I solved it commenting the line :
KUBELET_POD_INFRA_CONTAINER="--pod-infra-containerimage=registry.access.redhat.com/rhel7/pod-infrastructure:latest"
in /etc/kubernetes/kubelet
on each of my slaves
add a comment |Â
up vote
0
down vote
up vote
0
down vote
I solved it commenting the line :
KUBELET_POD_INFRA_CONTAINER="--pod-infra-containerimage=registry.access.redhat.com/rhel7/pod-infrastructure:latest"
in /etc/kubernetes/kubelet
on each of my slaves
I solved it commenting the line :
KUBELET_POD_INFRA_CONTAINER="--pod-infra-containerimage=registry.access.redhat.com/rhel7/pod-infrastructure:latest"
in /etc/kubernetes/kubelet
on each of my slaves
edited Nov 4 '17 at 3:18
Rui F Ribeiro
36k1271114
36k1271114
answered Nov 3 '17 at 20:21
inout
1
1
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f400938%2funable-to-pull-images-in-kubernetes%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password