Pods Stuck in ContainerCreating with 'failed to assign an IP address to container'kubernetes node doesn't get registeredkubernetes dial tcp i/o timeout error in version 1.7.0. Also kubeadm join command failsError in starting pods- kubernetes. Pods remain in ContainerCreating stateError syncing pod,failed for registry.access.redhat.com (Kubernetes)Kubernetes kube-dns Pause container in crashloop with Error adding network: failed to Statfs “/proc/54226/ns/net”:Kubernetes “Failed create pod sandbox” error when deploying services on Linux/Windows clusterkubernetes pods stuck at containercreatingPods stay in ContainerCreating state with “Failed create pod sandbox” messageUnable to ensure pod container exists: failed to create containerInitializing Tiller for Helm with Kubeadm - Kubernetes

Air travel with refrigerated insulin

"Marked down as someone wanting to sell shares." What does that mean?

How can a new country break out from a developed country without war?

How do I lift the insulation blower into the attic?

What (if any) is the reason to buy in small local stores?

What 1968 Moog synthesizer was used in the Movie Apollo 11?

Can you take a "free object interaction" while incapacitated?

What do the positive and negative (+/-) transmit and receive pins mean on Ethernet cables?

Connection Between Knot Theory and Number Theory

Is there a distance limit for minecart tracks?

How would a solely written language work mechanically

Would this string work as string?

Trouble reading roman numeral notation with flats

Asserting that Atheism and Theism are both faith based positions

Is there any common country to visit for persons holding UK and Schengen visas?

Control width of columns in a tabular environment

Offset in split text content

Writing in a Christian voice

Put the phone down / Put down the phone

Output visual diagram of picture

Not hide and seek

Could a welfare state co-exist with mega corporations?

Exposing a company lying about themselves in a tightly knit industry (videogames) : Is my career at risk on the long run?

Why is indicated airspeed rather than ground speed used during the takeoff roll?



Pods Stuck in ContainerCreating with 'failed to assign an IP address to container'


kubernetes node doesn't get registeredkubernetes dial tcp i/o timeout error in version 1.7.0. Also kubeadm join command failsError in starting pods- kubernetes. Pods remain in ContainerCreating stateError syncing pod,failed for registry.access.redhat.com (Kubernetes)Kubernetes kube-dns Pause container in crashloop with Error adding network: failed to Statfs “/proc/54226/ns/net”:Kubernetes “Failed create pod sandbox” error when deploying services on Linux/Windows clusterkubernetes pods stuck at containercreatingPods stay in ContainerCreating state with “Failed create pod sandbox” messageUnable to ensure pod container exists: failed to create containerInitializing Tiller for Helm with Kubeadm - Kubernetes













1















Issue



Two pods of my deployment are stuck in ContainerCreating with the message:



Failed create pod sandbox: rpc error: code = Unknown desc = NetworkPlugin cni failed to set up pod "etl-worker-87d885c45-g5q88_etl" network: add cmd: failed to assign an IP address to container



What I Tried



This thread suggested upgrading the CNI version to 1.3.2. from amazon-k8s-cni:1.0.0 with:



kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/master/config/v1.3/aws-k8s-cni.yaml



When I attempted to do this, the first rolled out nodes went into CrashLoopBackoff and when described showed the message:



Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.



... and then many of our worker pods requests began erroring out. So I ran kubectl rollout undo ds aws-node -n kube-system to undo what I had done.



More Info



I also installed cni-metrics-helper and this is a snapshot of the output. ipamdErr fluctuates a lot from 0 to 1.7k in Cloudwatch. I'm not really sure what that metric means though.



eniMaxAvailable: 60
assignIPAddresses: 656
ipamdErr: 308
eniAllocated: 60
totalIPAddresses: 660


Questions



What other configuration do I need to check or update before applying aws-k8s-cni.yaml?



Is there some other solution to fixing pods that are stuck in ContainerCreating with that error message?










share|improve this question






















  • do you have DNS service running?

    – Vishrant
    Mar 7 at 0:54











  • @Vishrant Yes. Running kube-dns deployment with 3 replicas.

    – ProGirlXOXO
    Mar 7 at 0:57











  • What instance type are you using?

    – Claes Mogren
    Mar 7 at 1:14











  • @ClaesMogren t2.large

    – ProGirlXOXO
    Mar 7 at 19:23











  • Problem was temporarily solved by simply deleting the pods that were stuck in ContainerCreating. Kubernetes should be handling this though. Still interested in proper way of upgrading CNI.

    – ProGirlXOXO
    Mar 7 at 22:03















1















Issue



Two pods of my deployment are stuck in ContainerCreating with the message:



Failed create pod sandbox: rpc error: code = Unknown desc = NetworkPlugin cni failed to set up pod "etl-worker-87d885c45-g5q88_etl" network: add cmd: failed to assign an IP address to container



What I Tried



This thread suggested upgrading the CNI version to 1.3.2. from amazon-k8s-cni:1.0.0 with:



kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/master/config/v1.3/aws-k8s-cni.yaml



When I attempted to do this, the first rolled out nodes went into CrashLoopBackoff and when described showed the message:



Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.



... and then many of our worker pods requests began erroring out. So I ran kubectl rollout undo ds aws-node -n kube-system to undo what I had done.



More Info



I also installed cni-metrics-helper and this is a snapshot of the output. ipamdErr fluctuates a lot from 0 to 1.7k in Cloudwatch. I'm not really sure what that metric means though.



eniMaxAvailable: 60
assignIPAddresses: 656
ipamdErr: 308
eniAllocated: 60
totalIPAddresses: 660


Questions



What other configuration do I need to check or update before applying aws-k8s-cni.yaml?



Is there some other solution to fixing pods that are stuck in ContainerCreating with that error message?










share|improve this question






















  • do you have DNS service running?

    – Vishrant
    Mar 7 at 0:54











  • @Vishrant Yes. Running kube-dns deployment with 3 replicas.

    – ProGirlXOXO
    Mar 7 at 0:57











  • What instance type are you using?

    – Claes Mogren
    Mar 7 at 1:14











  • @ClaesMogren t2.large

    – ProGirlXOXO
    Mar 7 at 19:23











  • Problem was temporarily solved by simply deleting the pods that were stuck in ContainerCreating. Kubernetes should be handling this though. Still interested in proper way of upgrading CNI.

    – ProGirlXOXO
    Mar 7 at 22:03













1












1








1








Issue



Two pods of my deployment are stuck in ContainerCreating with the message:



Failed create pod sandbox: rpc error: code = Unknown desc = NetworkPlugin cni failed to set up pod "etl-worker-87d885c45-g5q88_etl" network: add cmd: failed to assign an IP address to container



What I Tried



This thread suggested upgrading the CNI version to 1.3.2. from amazon-k8s-cni:1.0.0 with:



kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/master/config/v1.3/aws-k8s-cni.yaml



When I attempted to do this, the first rolled out nodes went into CrashLoopBackoff and when described showed the message:



Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.



... and then many of our worker pods requests began erroring out. So I ran kubectl rollout undo ds aws-node -n kube-system to undo what I had done.



More Info



I also installed cni-metrics-helper and this is a snapshot of the output. ipamdErr fluctuates a lot from 0 to 1.7k in Cloudwatch. I'm not really sure what that metric means though.



eniMaxAvailable: 60
assignIPAddresses: 656
ipamdErr: 308
eniAllocated: 60
totalIPAddresses: 660


Questions



What other configuration do I need to check or update before applying aws-k8s-cni.yaml?



Is there some other solution to fixing pods that are stuck in ContainerCreating with that error message?










share|improve this question














Issue



Two pods of my deployment are stuck in ContainerCreating with the message:



Failed create pod sandbox: rpc error: code = Unknown desc = NetworkPlugin cni failed to set up pod "etl-worker-87d885c45-g5q88_etl" network: add cmd: failed to assign an IP address to container



What I Tried



This thread suggested upgrading the CNI version to 1.3.2. from amazon-k8s-cni:1.0.0 with:



kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/master/config/v1.3/aws-k8s-cni.yaml



When I attempted to do this, the first rolled out nodes went into CrashLoopBackoff and when described showed the message:



Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.



... and then many of our worker pods requests began erroring out. So I ran kubectl rollout undo ds aws-node -n kube-system to undo what I had done.



More Info



I also installed cni-metrics-helper and this is a snapshot of the output. ipamdErr fluctuates a lot from 0 to 1.7k in Cloudwatch. I'm not really sure what that metric means though.



eniMaxAvailable: 60
assignIPAddresses: 656
ipamdErr: 308
eniAllocated: 60
totalIPAddresses: 660


Questions



What other configuration do I need to check or update before applying aws-k8s-cni.yaml?



Is there some other solution to fixing pods that are stuck in ContainerCreating with that error message?







kubernetes aws-eks






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 7 at 0:52









ProGirlXOXOProGirlXOXO

65531023




65531023












  • do you have DNS service running?

    – Vishrant
    Mar 7 at 0:54











  • @Vishrant Yes. Running kube-dns deployment with 3 replicas.

    – ProGirlXOXO
    Mar 7 at 0:57











  • What instance type are you using?

    – Claes Mogren
    Mar 7 at 1:14











  • @ClaesMogren t2.large

    – ProGirlXOXO
    Mar 7 at 19:23











  • Problem was temporarily solved by simply deleting the pods that were stuck in ContainerCreating. Kubernetes should be handling this though. Still interested in proper way of upgrading CNI.

    – ProGirlXOXO
    Mar 7 at 22:03

















  • do you have DNS service running?

    – Vishrant
    Mar 7 at 0:54











  • @Vishrant Yes. Running kube-dns deployment with 3 replicas.

    – ProGirlXOXO
    Mar 7 at 0:57











  • What instance type are you using?

    – Claes Mogren
    Mar 7 at 1:14











  • @ClaesMogren t2.large

    – ProGirlXOXO
    Mar 7 at 19:23











  • Problem was temporarily solved by simply deleting the pods that were stuck in ContainerCreating. Kubernetes should be handling this though. Still interested in proper way of upgrading CNI.

    – ProGirlXOXO
    Mar 7 at 22:03
















do you have DNS service running?

– Vishrant
Mar 7 at 0:54





do you have DNS service running?

– Vishrant
Mar 7 at 0:54













@Vishrant Yes. Running kube-dns deployment with 3 replicas.

– ProGirlXOXO
Mar 7 at 0:57





@Vishrant Yes. Running kube-dns deployment with 3 replicas.

– ProGirlXOXO
Mar 7 at 0:57













What instance type are you using?

– Claes Mogren
Mar 7 at 1:14





What instance type are you using?

– Claes Mogren
Mar 7 at 1:14













@ClaesMogren t2.large

– ProGirlXOXO
Mar 7 at 19:23





@ClaesMogren t2.large

– ProGirlXOXO
Mar 7 at 19:23













Problem was temporarily solved by simply deleting the pods that were stuck in ContainerCreating. Kubernetes should be handling this though. Still interested in proper way of upgrading CNI.

– ProGirlXOXO
Mar 7 at 22:03





Problem was temporarily solved by simply deleting the pods that were stuck in ContainerCreating. Kubernetes should be handling this though. Still interested in proper way of upgrading CNI.

– ProGirlXOXO
Mar 7 at 22:03












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55034437%2fpods-stuck-in-containercreating-with-failed-to-assign-an-ip-address-to-containe%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes















draft saved

draft discarded
















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55034437%2fpods-stuck-in-containercreating-with-failed-to-assign-an-ip-address-to-containe%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

AWS Lex not identifying response if by a variable The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) The Ask Question Wizard is Live! Data science time! April 2019 and salary with experienceEnforcing custom enumeration in AWS LEX for slot valuesHow to give response based on user response in Amazon Lex?Intercepting AWS Lambda Response to a AWS Lex QueryLex chat bot error: Reached second execution of fulfillment lambda on the same utteranceamazon lex showing invalid responseLambda response send back to Lex slot?Response card in Amazon lexAmazon Lex - Lambda response return HTML to botHow can I solve 424 (Failed Dependency) (python) obtained from Amazon lex?

Алба-Юлія

Захаров Федір Захарович