trachal
Members
-
Joined
-
Last visited
-
Issues with custom IPVLANL3 Docker network after the upgrade. All my dockers run on a custom IPVLANL3 network after the up grade none of the dockers will start and produce this error in the log “failed to create the ipvlan port: device or resource busy” The custom network is present and all dockers are assigned to it. If I roll back everything works correctly as it always has root@NAS1:~# docker network ls NETWORK ID NAME DRIVER SCOPE c672eff05a16 bridge bridge local 3bbd8bb2ae5c host host local de7e521a4485 ipvlan-l3 ipvlan local f6fe78a2336c none null local nas1-diagnostics-20230901-2323.zip
-
Issues with custom IPVLANL3 Docker network after the upgrade. All my dockers run on a custom IPVLANL3 network after the up grade none of the dockers will start and produce this error in the log “failed to create the ipvlan port: device or resource busy” The custom network is present and all dockers are assigned to it. If I roll back everything works correctly as it always has root@NAS1:~# docker network ls NETWORK ID NAME DRIVER SCOPE c672eff05a16 bridge bridge local 3bbd8bb2ae5c host host local de7e521a4485 ipvlan-l3 ipvlan local f6fe78a2336c none null local nas1-diagnostics-20230901-2323.zip