Gain access to wireless interface

I followed the information available here in order to get access to my wireless interface from within a docker container (I’m running kali-linux in there).

However, things seems to be slightly different on a Mac.
I do notice that, running with --net=host and --privileged gave me two more interfaces. Before I had only eth0 and lo. Now, I additionally have an eth1 and an interface called docker0.

However, when running iwconfig it says ‘no wireless extensions.’ for all of these. Here, I also see an additional interface ‘dummy0’ listed.

Not sure if it’s a different problem, or related, but this also doesn’t work:
root@main:/# airmon-ng
ls: cannot access ‘/sys/class/ieee80211/’: No such file or directory

Any hints? Thanks!

macOS High Sierra 10.13.4
Docker version 18.05.0-ce, build f150324

Hey @jonnez , so the issue is that since you are on mac and the docker is running inside a vm, the vm does not know about your host’s wifi device. Now docker only knows everything that is available on the vm since it is running in the vm, hence your docker container does not know about the wifi device. If you could somehow make the wifi device on host be available as wifi device inside vm then it will work.