If we enable or disable modules, that can cause problems. Maybe I am wrong, but Docker created the VM and can support Docker Desktop until we start to change it. Even if it had, I don’t think it would be a good idea to change the kernel module settings inside the VM. Write(2, "automount: test mount forbidden "., 118automount: test mount forbidden or incorrect kernel protocol version, kernel protocol version 5.00 or above required. Mount("automount", "/tmp/autolZdOE5", "autofs", MS_MGC_VAL, "fd=4,pgrp=458,minproto=3,maxprot".) = -1 ENODEV (No such device) Maybe macOS doesn’t provide autofs module with the version of the linux kernel that it provides? Modprobe: FATAL: Module autofs not found in directory /lib/modules/5.10.104-linuxkit In fact, I get this message when I try to load autofs modprobe autofs I am not sure what it means by “No such device”, but maybe it’s failing to find autofs module? When I run automount with strace, I get a bit more information and it looks like it’s failing to test mount? mount("automount", "/tmp/autolZdOE5", "autofs", MS_MGC_VAL, "fd=4,pgrp=458,minproto=3,maxprot".) = -1 ENODEV (No such device) Oddly, I am using the latest version of docker on the latest version of macOS (12.5.1 - Monterey) docker version
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |