Hello
since an update, I think in february, I have a problem to start up docker containers on my UCS 4.2 host.
existing containers work as expected but I can’t start newly created ones.
As it seems there is a problem with the network stack.
No IP adresse is assigned.
Syslog only says:
Apr 13 18:27:10 v22017054644049589 kernel: [4924117.626251] br-cd37ca14b53a: port 1(veth204c917) entered blocking state
Apr 13 18:27:10 v22017054644049589 kernel: [4924117.626254] br-cd37ca14b53a: port 1(veth204c917) entered disabled state
Apr 13 18:27:10 v22017054644049589 kernel: [4924117.626600] device veth204c917 entered promiscuous mode
Apr 13 18:27:10 v22017054644049589 kernel: [4924117.626753] IPv6: ADDRCONF(NETDEV_UP): veth204c917: link is not ready
Apr 13 18:27:10 v22017054644049589 kernel: [4924117.842061] eth0: renamed from vethb6f5f2c
Apr 13 18:27:10 v22017054644049589 kernel: [4924117.857806] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Apr 13 18:27:10 v22017054644049589 kernel: [4924117.858641] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Apr 13 18:27:10 v22017054644049589 kernel: [4924117.858674] IPv6: ADDRCONF(NETDEV_CHANGE): veth204c917: link becomes ready
Apr 13 18:27:10 v22017054644049589 kernel: [4924117.858729] br-cd37ca14b53a: port 1(veth204c917) entered blocking state
Apr 13 18:27:10 v22017054644049589 kernel: [4924117.858731] br-cd37ca14b53a: port 1(veth204c917) entered forwarding state
Apr 13 18:27:10 v22017054644049589 kernel: [4924117.977463] vethb6f5f2c: renamed from eth0
Apr 13 18:27:10 v22017054644049589 kernel: [4924118.018744] br-cd37ca14b53a: port 1(veth204c917) entered disabled state
Apr 13 18:27:10 v22017054644049589 kernel: [4924118.021403] br-cd37ca14b53a: port 1(veth204c917) entered disabled state
Apr 13 18:27:10 v22017054644049589 kernel: [4924118.022853] device veth204c917 left promiscuous mode
Apr 13 18:27:10 v22017054644049589 kernel: [4924118.022856] br-cd37ca14b53a: port 1(veth204c917) entered disabled state
Anybody an idea what the reason could be?
Thanks and regards!