I need help understanding my networking logs due to docker-compose networking.
I'm ssh'd into a VM, and I have two projects with docker-compose. The first is launched simply with docker-compose up. When I try to launch the second, my ssh session freezes, and I can no longer ssh into the VM. After lots of trial and error, and after reading this I tried to append to my 2nd project's docker-compose.yml file the following:
networks: default: external: name: ffamfe_default where ffamfe_default is the name of the network created by docker-compose up of the 1st project. With this, the docker-compose up on the 2nd project doesn't kick me out of the ssh session.
I tailed the logs in /var/log/*.log, and here's the output with the networks section in the docker-compose.yml file (without the timestamp prefix: Jan 19 09:13:42 hostname kernel: [420096.305357]):
aufs au_opts_verify:1597:dockerd[13813]: dirperm1 breaks the protection by the permission bits on the lower branch device veth6a84537 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth6a84537: link is not ready eth0: renamed from veth2480623 IPv6: ADDRCONF(NETDEV_CHANGE): veth6a84537: link becomes ready br-fe0deb0149df: port 18(veth6a84537) entered forwarding state br-fe0deb0149df: port 18(veth6a84537) entered forwarding state aufs au_opts_verify:1597:dockerd[25317]: dirperm1 breaks the protection by the permission bits on the lower branch device veth1a3c1e3 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth1a3c1e3: link is not ready br-fe0deb0149df: port 22(veth1a3c1e3) entered forwarding state br-fe0deb0149df: port 22(veth1a3c1e3) entered forwarding state eth0: renamed from veth54e576d IPv6: ADDRCONF(NETDEV_CHANGE): veth1a3c1e3: link becomes ready br-fe0deb0149df: port 22(veth1a3c1e3) entered disabled state veth54e576d: renamed from eth0 br-fe0deb0149df: port 22(veth1a3c1e3) entered disabled state device veth1a3c1e3 left promiscuous mode br-fe0deb0149df: port 22(veth1a3c1e3) entered disabled state br-fe0deb0149df: port 18(veth6a84537) entered forwarding state and here's the output without the networks section (i.e. when I get kicked out of the ssh session):
IPv6: ADDRCONF(NETDEV_UP): br-55349b03453a: link is not ready aufs au_opts_verify:1597:dockerd[26982]: dirperm1 breaks the protection by the permission bits on the lower branch aufs au_opts_verify:1597:dockerd[26982]: dirperm1 breaks the protection by the permission bits on the lower branch aufs au_opts_verify:1597:dockerd[3051]: dirperm1 breaks the protection by the permission bits on the lower branch device veth7a1bcde entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth7a1bcde: link is not ready br-55349b03453a: port 1(veth7a1bcde) entered forwarding state br-55349b03453a: port 1(veth7a1bcde) entered forwarding state br-55349b03453a: port 1(veth7a1bcde) entered disabled state eth0: renamed from veth5d8a2ea IPv6: ADDRCONF(NETDEV_CHANGE): veth7a1bcde: link becomes ready br-55349b03453a: port 1(veth7a1bcde) entered forwarding state br-55349b03453a: port 1(veth7a1bcde) entered forwarding state IPv6: ADDRCONF(NETDEV_CHANGE): br-55349b03453a: link becomes ready aufs au_opts_verify:1597:dockerd[13814]: dirperm1 breaks the protection by the permission bits on the lower branch aufs au_opts_verify:1597:dockerd[13814]: dirperm1 breaks the protection by the permission bits on the lower branch aufs au_opts_verify:1597:dockerd[13922]: dirperm1 breaks the protection by the permission bits on the lower branch device veth3253bd4 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth3253bd4: link is not ready br-55349b03453a: port 2(veth3253bd4) entered forwarding state br-55349b03453a: port 2(veth3253bd4) entered forwarding state br-55349b03453a: port 2(veth3253bd4) entered disabled state eth0: renamed from veth9c8aaa3 IPv6: ADDRCONF(NETDEV_CHANGE): veth3253bd4: link becomes ready br-55349b03453a: port 2(veth3253bd4) entered forwarding state br-55349b03453a: port 2(veth3253bd4) entered forwarding state br-55349b03453a: port 2(veth3253bd4) entered disabled state veth9c8aaa3: renamed from eth0 br-55349b03453a: port 2(veth3253bd4) entered disabled state device veth3253bd4 left promiscuous mode br-55349b03453a: port 2(veth3253bd4) entered disabled state br-55349b03453a: port 1(veth7a1bcde) entered forwarding state br-55349b03453a: port 1(veth7a1bcde) entered disabled state veth5d8a2ea: renamed from eth0 br-55349b03453a: port 1(veth7a1bcde) entered disabled state device veth7a1bcde left promiscuous mode br-55349b03453a: port 1(veth7a1bcde) entered disabled state I don't really understand how to read these logs. Here is my ifconfig also. Can someone help me read the logs and figure out what the problem is?
1 Answers
Answers 1
br-xxxxxxx are the bridge interfaces of Docker and vethxxxxxxx are the virtual interfaces of your containers, Docker use those veth interfaces but you do not directly interact on it, they use an IPv6 address and don't have IPv4. Docker can't create NAT interfaces, it can only create bridge and veth with IPv6 for containers. You can link your bridge to any physical or virtual interface of your host.
So it work like that:
eth0 (your interface or v-interface if you want) ↔ brxxxxx(docker bridge) ↔ vethxxxxx (v-interface of your container)
It's all I can say, I'm not sure that someone else will answer, there is not a lot of Docker experts, so I give you all informations I can to help you to understand your logs.
0 comments:
Post a Comment