Port of docker keep flapping

[Michael Huang]

recently, i noticed thousandeyes/enterprise-agent on my docker unstable.  in the log, i notice following errors:

 

Jul 31 14:45:38 Tower kernel: eth0: renamed from veth59412e0
Jul 31 14:45:46 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jul 31 14:45:46 Tower kernel: te-bbot-ipv4: port 1(veth6624a102) entered blocking state
Jul 31 14:45:46 Tower kernel: te-bbot-ipv4: port 1(veth6624a102) entered disabled state
Jul 31 14:45:46 Tower kernel: device veth6624a102 entered promiscuous mode
Jul 31 14:45:47 Tower kernel: te-bbot-ipv4: port 1(veth6624a102) entered blocking state
Jul 31 14:45:47 Tower kernel: te-bbot-ipv4: port 1(veth6624a102) entered forwarding state
Jul 31 14:45:48 Tower kernel: te-bbot-ipv4: port 1(veth6624a102) entered disabled state
Jul 31 14:45:48 Tower kernel: device veth6624a102 left promiscuous mode
Jul 31 14:45:48 Tower kernel: te-bbot-ipv4: port 1(veth6624a102) entered disabled state
Jul 31 14:45:49 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jul 31 14:45:49 Tower kernel: te-bbot-ipv4: port 1(vethf2ca2d71) entered blocking state
Jul 31 14:45:49 Tower kernel: te-bbot-ipv4: port 1(vethf2ca2d71) entered disabled state
Jul 31 14:45:49 Tower kernel: device vethf2ca2d71 entered promiscuous mode
Jul 31 14:45:49 Tower kernel: te-bbot-ipv4: port 1(vethf2ca2d71) entered blocking state
Jul 31 14:45:49 Tower kernel: te-bbot-ipv4: port 1(vethf2ca2d71) entered forwarding state
Jul 31 14:45:49 Tower kernel: te-bbot-ipv4: port 1(vethf2ca2d71) entered disabled state
Jul 31 14:45:49 Tower kernel: device vethf2ca2d71 left promiscuous mode
Jul 31 14:45:49 Tower kernel: te-bbot-ipv4: port 1(vethf2ca2d71) entered disabled state
Jul 31 14:45:50 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

 

so looks like the port is always flapping.  

 

i has been worked for several months without this error,  even on latest or old version.    and all others docker has no such issue. 

 

BTW,  my docker is using br1 which is eth1.   eth0 has no cable on it. 

 

and here is command to build docker:

docker run \
  --hostname='mk-TE' \
  --memory=2g \
  --memory-swap=2g \
  --detach=true \
  --tty=true \
  --shm-size=512M \

  -e TEAGENT_ACCOUNT_TOKEN=d812398jkjfadf38cgiap70s349cxfkl1qm \.  (i removed some digit here)
  -e TEAGENT_INET=4 \
  -v '/mnt/user/ThousandEyes/thousandeyes/mk-TE/te-agent':/var/lib/te-agent \
  -v '/mnt/user/ThousandEyes/thousandeyes/mk-TE/te-browserbot':/var/lib/te-browserbot \
  -v '/mnt/user/ThousandEyes/thousandeyes/mk-TE/log/':/var/log/agent \
  --cap-add=NET_ADMIN \
  --cap-add=SYS_ADMIN \
  --name 'mk-TE' \

  --net='br1' \

  --ip='10.0.0.30' \

  --restart=unless-stopped \

  --expose=49152/udp \

  --expose=49153/udp \

  --expose=49153/tcp \

  --publish=49152:49152/udp \

  --publish=49153:49153/udp \

  --publish=49153:49153/tcp \tower-diagnostics-20220731-1528.zip

  thousandeyes/enterprise-agent:latest /sbin/my_init 

[Squid]

The container is continually restarting (due to the --restart=unlessstopped)

 

you need to go through it's logs / setup and figure out why it's doing that

[Michael Huang]

21 hours ago, Squid said:

The container is continually restarting (due to the --restart=unlessstopped)

 

you need to go through it's logs / setup and figure out why it's doing that

 

Thanks. i think i found where the problem is.  looks like the depend lib is missing or apparmor is missing, so it cannot create te-browserbot pod.   anyway, i will use ubuntu instead.