-
Notifications
You must be signed in to change notification settings - Fork 950
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug report] network p0 create failed when reboot #2618
Comments
Thanks a lot for your feedback. |
@allencloud I update the issue with log appended. |
journalctl
|
@elvizlai Can you provide all the network information, |
@rudyfly First time init, the when reboot, the p0 and vetha49ec6b(created by pouch run) is gone.
|
set container restart=always, it will start when daemon recover, while it will set into activeSandbox and cause network can't be initialized, so bridge |
Do we have any solutions? @rudyfly |
I faced the same problem |
Thanks for your report, @elvizlai |
问题描述:
操作如下:
之后在命令如问题描述所示
|
Ⅰ. Issue Description
Ⅱ. Describe what happened
Root VPC, some container(not all) not started and because missing pouch
p0
net interface.After reboot, MUSTsystemctl restart pouch
to recreate p0, thenpouch start container
manually.If there are any container can start(--restart always), then p0 won't create.
example:
I think p0 MUST create before vetheXXXX.
ifconfig
Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)
the container is not started as expected.
Ⅴ. Anything else we need to know?
systemctl staus pouch -l
Ⅵ. Environment:
pouch version
):latest
centos7
uname -a
):4.20
The text was updated successfully, but these errors were encountered: