Outlet6957

Did you ever get this working in ComfyUI? I have the EXACT same issue. If so, what was the fix?

Anyone know why this happens with latest update (05-comfy-ui) 04/15/2024 08:40:42 PM Prestartup times for custom nodes: 04/15/2024 08:40:42 PM 0.9 seconds: /config/05-comfy-ui/ComfyUI/custom_nodes/ComfyUI-Manager 04/15/2024 08:40:42 PM 04/15/2024 08:40:54 PM Total VRAM 12037 MB, total RAM 96462 MB 04/15/2024 08:40:54 PM Set vram state to: NORMAL_VRAM 04/15/2024 08:40:54 PM Device: cuda:0 NVIDIA GeForce RTX 3060 : cudaMallocAsync 04/15/2024 08:40:54 PM VAE dtype: torch.bfloat16 04/15/2024 08:41:02 PM Using pytorch cross attention 04/15/2024 08:41:09 PM Traceback (most recent call last): 04/15/2024 08:41:09 PM File "/config/05-comfy-ui/ComfyUI/nodes.py", line 1864, in load_custom_node 04/15/2024 08:41:09 PM module_spec.loader.exec_module(module) 04/15/2024 08:41:09 PM File "<frozen importlib._bootstrap_external>", line 940, in exec_module 04/15/2024 08:41:09 PM File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed 04/15/2024 08:41:09 PM File "/config/05-comfy-ui/ComfyUI/custom_nodes/ComfyUI-Manager/__init__.py", line 18, in <module> 04/15/2024 08:41:09 PM from .glob import manager_core as core 04/15/2024 08:41:09 PM File "/config/05-comfy-ui/ComfyUI/custom_nodes/ComfyUI-Manager/glob/manager_core.py", line 9, in <module> 04/15/2024 08:41:09 PM import git 04/15/2024 08:41:09 PM ModuleNotFoundError: No module named 'git' 04/15/2024 08:41:09 PM 04/15/2024 08:41:09 PM Cannot import /config/05-comfy-ui/ComfyUI/custom_nodes/ComfyUI-Manager module for custom nodes: No module named 'git' 04/15/2024 08:41:09 PM 04/15/2024 08:41:09 PM Import times for custom nodes: 04/15/2024 08:41:09 PM 0.0 seconds: /config/05-comfy-ui/ComfyUI/custom_nodes/websocket_image_save.py 04/15/2024 08:41:09 PM 0.1 seconds (IMPORT FAILED): /config/05-comfy-ui/ComfyUI/custom_nodes/ComfyUI-Manager 04/15/2024 08:41:09 PM 04/15/2024 08:41:09 PM Setting output directory to: /config/outputs/05-comfy-ui 04/15/2024 08:41:09 PM Starting server 04/15/2024 08:41:09 PM 04/15/2024 08:41:09 PM To see the GUI go to: http://0.0.0.0:9000

Oh also, the https://github.com/facefusion/facefusion uses pytorch now instead of tensorflow but the one within the hollafain uses tensorflow for some reason even though the script pulls from the original repo, thus creating that issue as well. I'll check this out later tonight and see if I can push a change to their github

No but I did find a solution that needs to be tested. Apparently when you install extensions they install the onnx-runtime which creates a conflict with existing onnx files. When this happens it disables the CUDA. But again, I have not tested this out. If I do I will report back here and tag you.

Bruh, you are a champion. Thank you and happy holidays!

Ok I've done some digging. If I add face fusion via the docker settings or within automatic1111 extensions, it does not detect GPU thus not giving me a "CUDA" option. The container works fine with the GPU for generating art, and device shows up in nvidia-smi when you docker exec into the container. However if I activate the venv within the docker container and run python3 -c "import tensorflow; print(tensorflow.config.experimental.list_physical_devices('GPU'))" It returns [] For some reason tensorflow does not detect GPU and facefusion needs that detection for it to provide the CUDA option. Any thoughts?

I know you mentioned some models are not production ready. Face fusion included. Is that warning the reason I don't see "CUDA" as a provider on the face fusion webui?

agreed

Thank you for the awesome plugin and keeping the nerd packages alive. Could you please add ripgrep?

Question, if I set the bonding mode to NO as indicated, how do you access VMs now? They pull the 122.X network address due to BR0 going away from using that setting.

I am having this same issue. Any custom dockers I create will not boot up after I reboot the server. It says network id not found and I have to recreate the containers. Did you ever find a fix for this?

I can get this up and running by modifying a shell file within the docker container itself. However I am curious why the environment variable BLUEIRIS_VERSION=4 does not work.

Jesus christ, thank you so much. I was going nuts. I used a password manager to generate the DB password and it had some symbols in it to include a '#'. I appreciate you!!

You can reduce the size by converting to a QCOW2 image instead. It is MUCH smaller than the .img file above. The command for that is this qemu-img convert -f vmdk -O qcow2 ./GNS3_VM-disk1.vmdk ./GNS3VM-disk1.qcow2 I've been running GNS3 for about 2 years now with this method. Here are my file sizes for reference 1.5G ./GNS3VM-disk1.qcow2 42M ./GNS3VM-disk2.qcow2 532M ./GNS3_VM-disk1.vmdk 1.9M ./GNS3_VM-disk2.vmdk As far as the settings for the VM, the only thing I changed was the bios stays SeaBIOS but the Machine is i440fx-4.2. Also the Primary vDisk Bus is now SCSI instead of SATA. Let me know if you get stuck!