Udev is a daemon, not a service (aka it’s not listening any network port)
Using --net=host wont allow your container to talk to a daemon on the host.
I havent checked the details but as far as I know, the events that udev trigger goes to HAL through dbus. You probably want to share your host dbus socket directory (/run/dbus on my debian sid) with your container.
EDIT: nope. That’s not how udevadm works. It doesnt use dbus (unlike HAL).
Running the command strace udevadm monitor show that udevadm connect to udev using udev own socket which on my debian is at : /run/udev/control. That’s what you have to share with your container (a volume will do)