Containerlab failed to create some nodes and links in a large topology deployment: context deadline exceeded #1803
-
Describe the bug To Reproduce
Expected behavior: Actual behavior: any solutions please.. 😢 |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
Alright, so the container nodes, that make it into the link creation phase should all be deployed and running. Usually the |
Beta Was this translation helpful? Give feedback.
-
Using the --max-workers option can solve this problem, thank you very much.
…------------------ 原始邮件 ------------------
发件人: "Markus ***@***.***>;
发送时间: 2023年12月28日(星期四) 下午4:05
收件人: ***@***.***>;
抄送: ***@***.***>; ***@***.***>;
主题: Re: [srl-labs/containerlab] Containerlab failed to create some nodes and links in a large topology deployment: context deadline exceeded (Discussion #1803)
Alright, so the container nodes, that make it into the link creation phase should all be deployed and running. Usually the failed to Statfs message indicates that the referenced container is not running any more. If you check the state via docker ps you should be able to verify that. Further you should check the logs, to figure out why the container is not running any more.
Are you sure it is not a matter of resource shortage? Your're maybe running low on memory...
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Yes, using the --timeout or --max-workers option can solve this problem, thank you very much.
…------------------ 原始邮件 ------------------
发件人: "Markus ***@***.***>;
发送时间: 2023年12月28日(星期四) 下午4:14
收件人: ***@***.***>;
抄送: ***@***.***>; ***@***.***>;
主题: Re: [srl-labs/containerlab] Containerlab failed to create some nodes and links in a large topology deployment: context deadline exceeded (Discussion #1803)
Further I see you get context deadline exceeded messages.
To prevent these you might need to increate the timeout.
Global Flags: ... --timeout duration timeout for external API requests (e.g. container runtimes), e.g: 30s, 1m, 2m30s (default 2m0s) ...
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
Alright, so the container nodes, that make it into the link creation phase should all be deployed and running. Usually the
failed to Statfs
message indicates that the referenced container is not running any more. If you check the state viadocker ps
you should be able to verify that. Further you should check the logs, to figure out why the container is not running any more.Are you sure it is not a matter of resource shortage? Your're maybe running low on memory...