Yanqiang Miao
Yanqiang Miao
@grahamwhaley Thanks for your reply, have updated, expect to get your help. :-)
@grahamwhaley I create a container via `docker run -ti -d busybox top`, successful. ```bash # ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback...
ping @amshinde @chavafg Could you help me and give some guidance advice for this scenario? tks :)
>@miaoyq I'd like some clarifications on your issue here. You're saying that creating a pod with k8s, using the command kubectl create -f myapp.yaml, messes the network on your host...
>@miaoyq what is network configuration you are using for k8s? @jcvenegas Sorry, I am not very familiar with network，how can I find the network configuration?
@jcvenegas ```bash # ifconfig br-0a7129f645d4 Link encap:Ethernet HWaddr 02:42:c4:9c:4c:00 inet addr:172.18.0.1 Bcast:0.0.0.0 Mask:255.255.0.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0...
@sboeuf On my host.
`ens3` and `ens6` are used to connect other host in subnet, and connect to the Internet. I have to restart my system
This is the related log ([syslog.txt](https://github.com/clearcontainers/runtime/files/1600630/syslog.txt)) when I created a pod.
@grahamwhaley @jcvenegas @sboeuf Thank you very much for your help, I think I should go to sleep, continue tomorrow :-)