systemd:docker.service:Failed with result'start-limit-hit'.
# journalctl -xe
dockerd:unable toconfigure the Docker daemon with fileetc/docker/daemon.json:the following directives are specified both asaflag andinthe configuration file:hosts:(from flag:[fd://],from file:[unix:///var/run/docker.socktcp://0.0.0.0:56379])
systemd:docker.service:Main process exited,code=exited,status=1/FAILURE
A previous version of this post included advice to add two VMX file entries (efi.legacyBoot.enabled and efi.bootOrder) as part of the solution. These two settings should NOT be used. Instead, following the directions below. ——– You should be able to pass a single GPU (that is, half of a K80) to a VM running on ESX 6 by creating an EFI-bootable VM, doing an EFI installation of your guest OS, and then adding the following to the VM’s VMX file. pciPassthru.use64bitMMIO=”TRUE” Trying to pass more than one of these GPUs into the same VM will currently hit a platform memory limit and the VM will fail to boot. (NOTE: This limit has been removed in ESX 6.5). A smaller card like the K2 does not have this issue: GPGPU Blog Entry If the above does not work for you, send me email directly at “simons at vmware dot com”. In either case, please share your experience with others on the thread. And if you have any other questions about running HPC applications in a VMware environment, I’d be happy to hear from you directly. If you are interested in learning more of what we’ve been doing related to HPC, you can check out our HPC entries on the VMware CTO blog site here: HPC Blog Entries
Josh Simons High Performance Computing Office of the CTO VMware, Inc.