January 10, 20251 yr Author 2 hours ago, martial said: I will likely make an official release (once I update the unraid template and clean up the readme) this week end. 2 hours ago, DeusVault said: trying it now... .... and it worked 100% xlabs nodes installed! It was installed direct over the last install that we had worked on. Official release published. Feel free to use the original tag for the container
January 11, 20251 yr Wow - very excited to have found this project. I've been working in ComfyUI for the better part of a year and recently become rather uncomfortable with running it in my main Ubuntu Desktop VM given how many community modules are included in my installation. For all the obvious reasons, I want to containerize the ComfyUI instance and was dreading having to put all that together myself. Thanks so much for all the posts here, I'm looking forward to digging in. One quick qualifying question before I go down the wrong path: If I've bound my GPU to my Ubuntu VM (via IOMMU groups) because that's my desktop daily driver, should I pursue running the docker hub version of this container inside my VM? (instead of the Unraid plugin) Edited January 11, 20251 yr by chronocide
January 11, 20251 yr Author 19 hours ago, chronocide said: Wow - very excited to have found this project. I've been working in ComfyUI for the better part of a year and recently become rather uncomfortable with running it in my main Ubuntu Desktop VM given how many community modules are included in my installation. For all the obvious reasons, I want to containerize the ComfyUI instance and was dreading having to put all that together myself. Thanks so much for all the posts here, I'm looking forward to digging in. One quick qualifying question before I go down the wrong path: If I've bound my GPU to my Ubuntu VM (via IOMMU groups) because that's my desktop daily driver, should I pursue running the docker hub version of this container inside my VM? (instead of the Unraid plugin) The VM has the passthrough to your GPU. As such, yes, I would recommend running it either from the docker command line or docker compose (or Dockge if you have that running) within the VM as a container For any, you will want to have created a "run" directory owned by the user to place models and others in the ComfyUI/models folder before continuing. For docker (as detailed in the README.md or on DockerHub): docker run --rm -it --runtime nvidia --gpus all -v `pwd`/run:/comfy/mnt -e WANTED_UID=`id -u` -e WANTED_GID=`id -g` -e SECURITY_LEVEL=normal -p 8188:8188 --name comfyui-nvidia mmartial/comfyui-nvidia-docker:latest For docker-compose, see https://github.com/mmartial/ComfyUI-Nvidia-Docker?tab=readme-ov-file#22-docker-compose For Dockge, see https://blg.gkr.one/20240706-dockge/#175c678a0f6980f8bb9bf530abb0b8e6 Edited January 11, 20251 yr by martial
January 17, 20251 yr AttributeError: module 'pkgutil' has no attribute 'ImpImporter'. Did you mean: 'zipimporter'? [DONE] Security scan ## ComfyUI-Manager: installing dependencies done. ** ComfyUI startup time: 2025-01-17 14:19:45.217257 ** Platform: Linux ** Python version: 3.12.3 (main, Nov 6 2024, 18:32:19) [GCC 13.2.0] ** Python executable: /comfy/mnt/venv/bin/python3 ** ComfyUI Path: /comfy/mnt/ComfyUI ** Log path: /comfy/mnt/ComfyUI/comfyui.log ComfyUI failed or exited with an error Was working fine before the last update - is this just me? Did the recommended reinstall with a new run folder and copied all the models, inputs, outputs, custom nodes. Then after some a few restarts and custom model updates / try fixes. All looks good again (if anyone hits it) Edited January 17, 20251 yr by Plutini
January 18, 20251 yr Author 4 hours ago, Plutini said: AttributeError: module 'pkgutil' has no attribute 'ImpImporter'. Did you mean: 'zipimporter'? [DONE] Security scan ## ComfyUI-Manager: installing dependencies done. ** ComfyUI startup time: 2025-01-17 14:19:45.217257 ** Platform: Linux ** Python version: 3.12.3 (main, Nov 6 2024, 18:32:19) [GCC 13.2.0] ** Python executable: /comfy/mnt/venv/bin/python3 ** ComfyUI Path: /comfy/mnt/ComfyUI ** Log path: /comfy/mnt/ComfyUI/comfyui.log ComfyUI failed or exited with an error Was working fine before the last update - is this just me? Did the recommended reinstall with a new run folder and copied all the models, inputs, outputs, custom nodes. Then after some a few restarts and custom model updates / try fixes. All looks good again (if anyone hits it) My apologies about this. I had done a lot of local testing on that latest update to avoid issues, including filing an error report with ComfyUI Manager because of problems with the cm-cli. During my local testing, using the method described in https://github.com/mmartial/ComfyUI-Nvidia-Docker?tab=readme-ov-file#512-fixing-failed-custom-nodes fixed my issues, which mainly involved "start the Manager -> Custom Nodes Manager, Filter by Import Failed and use the Try fix button as this will download required packages and install those in the used venv." Still, the error you listed appears not to have been fixed by this step. Renaming the run directory is the proper workaround when this does not fix those issues. I am glad to hear it was resolved for you. That new version mainly brought us to an Ubuntu 24 base image (from 22) while updating the core CUDA version, allowing us to be a little ahead of the PyTorch-supporting content. Edited January 18, 20251 yr by martial
February 3, 20251 yr Author FYSA, a new release of the container (20250202) uses the new command-line option (—-base-directory), which allows the separation of the ComfyUI sources from the user's content (models, input, output, custom_nodes, user). You can use this to place the `basedir` on a separate volume, outside of the `appdata` folder. For new users, this should work out of the box, manually adapt the `basedir` mount location to reflect the preferred location. This option was recently added to ComfyUI. For users with a ComfyUI that was not "git pulled" within the last week, you must upgrade the code using the manager before enabling the variable. If you already have a large model collection, I recommend manually moving the "run/ComfyUI/models" to the new "basedir" as documented at https://github.com/mmartial/ComfyUI-Nvidia-Docker?tab=readme-ov-file#533-base_directory The template has been updated to reflect this change. This is the "basedir" variable (and its matching "BASE_DIRECTORY" hidden value) For people using the "user_script.bash", you need to add "${COMFY_CMDLINE_EXTRA}" to your "python3 ./main.py" line. For details, see https://github.com/mmartial/ComfyUI-Nvidia-Docker?tab=readme-ov-file#52-user_scriptbash Edited February 4, 20251 yr by martial
February 3, 20251 yr Does this container require a certain generation of graphics card? I have a Tesla P40 in my system with the latest Nvidia driver installed (545.29.06), which has me using Cuda 12.3 according to Nvidia-smi. However, when I try to install this container using the latest, it throws the error docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy' nvidia-container-cli: requirement error: unsatisfied condition: cuda>=12.5, please update your driver to a newer version, or use an earlier cuda container: unknown. Is there some way to force a earlier cuda version to match my installation? Apologies if this is a simple question, I am just starting to dabble in AI and have been having fun with Invoke, but it sounds like Comfy is the superior software.
February 3, 20251 yr Author 2 hours ago, MOEman365 said: Does this container require a certain generation of graphics card? I have a Tesla P40 in my system with the latest Nvidia driver installed (545.29.06), which has me using Cuda 12.3 according to Nvidia-smi. However, when I try to install this container using the latest, it throws the error docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy' nvidia-container-cli: requirement error: unsatisfied condition: cuda>=12.5, please update your driver to a newer version, or use an earlier cuda container: unknown. Is there some way to force a earlier cuda version to match my installation? Apologies if this is a simple question, I am just starting to dabble in AI and have been having fun with Invoke, but it sounds like Comfy is the superior software. Yes you can, when you performed the installation, there should have been a prompt that listed the available versions for the container. One of those was "ubuntu22_cuda12.3.2". Does your "nvidia-smi" show 12.3 or above 12.3.2 (it is likely possible to do a custom build with 12.3.0 as long as the base container is available from Docker Hub) Edited February 3, 20251 yr by martial
February 3, 20251 yr Unfortunately it shows 12.3 flat. And when I try to install the older container for 12.3.2 I get a different error: Unable to find image 'mmartial/comfyui-nvidia-docker:ubuntu22_cuda12.3.2' locally docker: Error response from daemon: manifest for mmartial/comfyui-nvidia-docker:ubuntu22_cuda12.3.2 not found: manifest unknown: manifest unknown. See 'docker run --help'
February 3, 20251 yr Author 20 minutes ago, MOEman365 said: Unfortunately it shows 12.3 flat. And when I try to install the older container for 12.3.2 I get a different error: Unable to find image 'mmartial/comfyui-nvidia-docker:ubuntu22_cuda12.3.2' locally docker: Error response from daemon: manifest for mmartial/comfyui-nvidia-docker:ubuntu22_cuda12.3.2 not found: manifest unknown: manifest unknown. See 'docker run --help' try with the "ubuntu22_cuda12.3.2-latest" tag? https://hub.docker.com/r/mmartial/comfyui-nvidia-docker/tags
February 3, 20251 yr That does seem to have fixed it! It loaded and I can currently get to the Web-UI. No models loaded yet or anything, and I won't have time to play with it for a while, but thank you so much for the help!
February 5, 20251 yr Hi martial, I attempted to update, failed. I then uninstalled, deleted all files, and attempted to start again - installed and failed. Tried all of the versions the only one that would not failed to install was the latest, but it did fail to complete its start up. I, once again, am at a loss. I am posting the only log I could capture. docker.log.2.4.2025
February 5, 20251 yr Author 1 hour ago, DeusVault said: Hi martial, I attempted to update, failed. I then uninstalled, deleted all files, and attempted to start again - installed and failed. Tried all of the versions the only one that would not failed to install was the latest, but it did fail to complete its start up. I, once again, am at a loss. I am posting the only log I could capture. docker.log.2.4.2025 2.54 kB · 0 downloads This is very strange: "warning: unable to unlink '/comfy/mnt/ComfyUI/.git/HEAD.lock': Transport endpoint is not connected" This looks like a fuse error to me; i.e. you tried to delete the content, but there is still an entry in the OS's internal mount table (bind mount) about this file ... you can not delete it And everything else crashes because of it. I recommend one of two options: 1) do a clean installation in a new "/mnt/user/appdata/nvidia-docker2" folder (note the 2) 2) reboot your host (if you need another reason, there is a new Nvidia driver available). This will clear the bind and you should be able to delete the directories after. I would try 1) first, as it will likely work PS: If you do 1) you can also do a secondary installation (Apps -> Settings -> Allow install of second instance) into that new folder; this will allow you to benefit from the latest "basedir" option to separate the code and venv (10GB or so) from the models and custom nodes, etc (usually WAY bigger); place "basedir" on another disk. This is also useful if you have the appdata backup enabled ... it will lower the size of your backup
February 5, 20251 yr Author A note of RTX 5080/5090 support: it is still in beta. 1) you will need the latest (very latest) NVIDIA driver (570) 2) you will need to MANUALLY change the container tag from `latest` to `ubuntu24_cuda12.8-latest` For the curious, I posted more details at I will not update this post when the final Torch release supporting 12.8 is out, but it will likely be in the first post of this topic. PS1: no I do not have a 5090 yet (like a lot of people who tried honestly to get one) PS2: if you can help me purchase a 5090 FE so I can test.... -- a man can dream, right
February 7, 20251 yr Author On 2/4/2025 at 9:11 PM, martial said: This is very strange: "warning: unable to unlink '/comfy/mnt/ComfyUI/.git/HEAD.lock': Transport endpoint is not connected" This looks like a fuse error to me;[...] PS: If you do 1) you can also do a secondary installation (Apps -> Settings -> Allow install of second instance) into that new folder; this will allow you to benefit from the latest "basedir" option to separate the code and venv (10GB or so) from the models and custom nodes, etc (usually WAY bigger); place "basedir" on another disk. This is also useful if you have the appdata backup enabled ... it will lower the size of your backup @DeusVault just checking if that helped
February 12, 20251 yr First just want to say that I love this container and have been using it very frequently for a while now successfully. I run with over 20 custom nodes on my usual workflows and have great success with this container. This last update though with the basedir option I wasn't able to upgrade properly and had to start fresh, not a problem its easy for me to do this. But I ran into 2 issues this latest update, first one I've already found a workaround but want to note it. With the Mikey Nodes node (and another one I can't remember) I get an error when installing them the first time, looking at the logs though I noticed it was trying to find the comfy_extras folder located 'basedir/comfy_extras/' instead of 'mnt/ComfyUI/comfy_extras/'. I was able to fix this by copying the existing '/mnt/ComfyUI/comfy_extras/' folder here: 'basedir/comfy_extras/' and clicking 'try fix' in the Manager. Since other nodes didn't present this issue I figure this has something to do with the way that specific nodes is looking for that folder, but in-case someone else has this issue this could be a workaround. Another issue I've yet to figure out but it's not a big deal to me has to do with the ControlNet Preprocessor node found in ComfyUI ArtVenture. This node appears to install fine, but when using the specific node (ControlNet Preprocessor) to process an image into like a depth/lineart or other controlnet map you can't select the preprocessor in the node. I believe it is supposed to download the preprocessors when the node is installed. I do see an open issue for this in the ArtVenture github so it might have nothing to do with this container specifically but figured I'd just let you know how my experience was. Thanks for maintaining this container, I don't know what I would do without it! Edited February 12, 20251 yr by SeldomNosePicker
February 13, 20251 yr Author 8 hours ago, SeldomNosePicker said: First just want to say that I love this container and have been using it very frequently for a while now successfully. I run with over 20 custom nodes on my usual workflows and have great success with this container. This last update though with the basedir option I wasn't able to upgrade properly and had to start fresh, not a problem its easy for me to do this. But I ran into 2 issues this latest update, first one I've already found a workaround but want to note it. With the Mikey Nodes node (and another one I can't remember) I get an error when installing them the first time, looking at the logs though I noticed it was trying to find the comfy_extras folder located 'basedir/comfy_extras/' instead of 'mnt/ComfyUI/comfy_extras/'. I was able to fix this by copying the existing '/mnt/ComfyUI/comfy_extras/' folder here: 'basedir/comfy_extras/' and clicking 'try fix' in the Manager. Since other nodes didn't present this issue I figure this has something to do with the way that specific nodes is looking for that folder, but in-case someone else has this issue this could be a workaround. Another issue I've yet to figure out but it's not a big deal to me has to do with the ControlNet Preprocessor node found in ComfyUI ArtVenture. This node appears to install fine, but when using the specific node (ControlNet Preprocessor) to process an image into like a depth/lineart or other controlnet map you can't select the preprocessor in the node. I believe it is supposed to download the preprocessors when the node is installed. I do see an open issue for this in the ArtVenture github so it might have nothing to do with this container specifically but figured I'd just let you know how my experience was. Thanks for maintaining this container, I don't know what I would do without it! Thanks for the kind words, I too am using it a lot, I have I think over 150 custom nodes in there from trying new workflows (and check if they work ... always in search of the best upscale-embedded workflow and such ) Apologies for this issue with basedir. I checked the PR that added it, as seen at https://github.com/comfyanonymous/ComfyUI/pull/6600/files, but I did not see "comfy_extras" as supposedly being in there. But I see the problem in my logs "FileNotFoundError: [Errno 2] No such file or directory: '/basedir/comfy_extras/nodes_clip_sdxl.py'" Apologies, adding a new Issue referencing this and will fix it shortly Once I fix this (hopefully today or tomorrow), I will take a look at the other controller. Got a workflow to test it?
February 13, 20251 yr Author @SeldomNosePicker UPDATE 20250214: I have posted a PR for mikeys_nodes that fixes the issue on their end I have closed the WiP branch as I am not making changes to the code to fix this UPDATE 20250213: I am consolidating updates within this https://github.com/mmartial/ComfyUI-Nvidia-Docker/issues/17 I confirm this appears to be custom nodes specific and comfy_extras should stay within the ComfyUI folder. OLDER: The strange thing is that this might not be correct. When I move comfy_extras into "basedir" every single one fails to load. I expect the reason it is working for you is that you did a `git pull` That pull re-created the content within the source ComfyUI directory, and things worked again. The issue with this is that content is then out of sync (if the git pull brought updated files) I have posted a question in Comfy's Discord; if I do not get feedback on it, I might need to post an issue. My current proposal is NOT to move the content of comfy_extras but at least create the folder in "basedir" so that "custom_nodes" can place content there if needed. That will not solve my "nodes_clip_sdxl.py" error since it is in the "ComfyUI" folder, but --at least for my test install-- it hopefully will not create issues I am not posting a new release until I get clarifications from the Comfy team. Edited February 15, 20251 yr by martial
February 13, 20251 yr I would like to request that the docker template be adjusted to utilize the --output-directory command line flag to specify an output directory separate from the directory where I store my checkpoints/loras/embeddings/etc. I have my checkpoints/loras/embeddings stored in a directory on a SSD, and I don't want to be writing continuously to that SSD with the output of my image generations. With the addition of the /basedir feature, the default behavior is to have the output folder in the same base directory as the inputs. Fortunately, by utilizing the --output-directory command line flag, we are able to specify a location outside of the base directory to output images to. However, in order to move it away from the same drive as the base directory, the docker needs to have an additional path added to it which points towards where you want to output images to. I've done this on my end as shown in the screenshot: While it was not difficult to work this out, I feel that other users would find it more convenient if the docker config already included the field to identify the output path, and the --output-directory command line flag was built into the docker by default.
February 13, 20251 yr Author 7 hours ago, bubo said: I would like to request that the docker template be adjusted to utilize the --output-directory command line flag to specify an output directory separate from the directory where I store my checkpoints/loras/embeddings/etc. I have my checkpoints/loras/embeddings stored in a directory on a SSD, and I don't want to be writing continuously to that SSD with the output of my image generations. With the addition of the /basedir feature, the default behavior is to have the output folder in the same base directory as the inputs. Fortunately, by utilizing the --output-directory command line flag, we are able to specify a location outside of the base directory to output images to. However, in order to move it away from the same drive as the base directory, the docker needs to have an additional path added to it which points towards where you want to output images to. I've done this on my end as shown in the screenshot: While it was not difficult to work this out, I feel that other users would find it more convenient if the docker config already included the field to identify the output path, and the --output-directory command line flag was built into the docker by default. Thanks for the question. I agree about having a separate directory for output. The good news is that at the end of January, the Comfy team integrated a new option to the ComfyUI CLI (--base-directory), and I have integrated it into the container and updated the Unraid template to reflect the change. You can see below a screenshot how what the template should show you at this point. I had to install a second instance of the container (turn off the first one, change the port) and install a new instance with the same parameters (locations) to use the updated template. My recommendation is to FIRST use the old container to update ComfyUI through the Manager so your container supports the new CLI option.. Then, manually create the new "basedir" folder before moving the files (you can do this using an SSH into your Unraid, a terminal from the WebUI, or a File Manager WebUI such as Double Commander). The reason behind this recommendation is that the container, when started, will attempt to MOVE "input, output, ... " (see list in the screenshot) to that location. That process is extremely slow because it will copy one file per file before deleting the folder. Not only is it slow, but if you have a large model collection, it will duplicate all the content on disk before deleting it. That solution also allows you to separate the "run" folder from the "basedir," which can be placed on an alternate disk (let's say you have a Docker Application backup running every day; not having the models as part of that backup is very convenient). Please see the last paragraph of this post for details on installing a second instance. Edited February 14, 20251 yr by martial
February 14, 20251 yr I was not specific enough. What I'm requesting is an additional parameter besides the Base Directory option. I'm already using the base directory option in the new template. The behavior of the base directory option by itself is to have the Output folder in the same base directory as the Inputs (checkpoints/loras/embeddings/etc). Many people put their inputs in a SSD to facilitate load times, and some of them may not want to have their generated images output to the same SSD due to size and repeated write concerns. ComfyUI allows for the separation of the Output Folder from the Base Directory folder via the --output-directory command line flag, but in order to utilize that flag to put the Output folder anywhere besides the Base Directory folder in the current Docker template requires an additional field to allow the user to specify where the Output folder resides in the array. As shown in my screenshot, it's not difficult to get it working. However, I think that many users would prefer having that field added as part of the default Docker installation, and the corresponding --output-directory command line flag incorporated into the docker instead of needing to be manually entered into the COMFY_CMDLINE_EXTRA field.
February 15, 20251 yr Hello. This stopped working for me so i uninstalled it and reinstalled and i still can not get it to work. I have the following in end of the logs. Let me know if there is anything else that is needed to help. Thanks for your time Unriaid 6.12.9 usage: main.py [-h] [--listen [IP]] [--port PORT] [--tls-keyfile TLS_KEYFILE] [--tls-certfile TLS_CERTFILE] [--enable-cors-header [ORIGIN]] [--max-upload-size MAX_UPLOAD_SIZE] [--extra-model-paths-config PATH [PATH ...]] [--output-directory OUTPUT_DIRECTORY] [--temp-directory TEMP_DIRECTORY] [--input-directory INPUT_DIRECTORY] [--auto-launch] [--disable-auto-launch] [--cuda-device DEVICE_ID] [--cuda-malloc | --disable-cuda-malloc] [--force-fp32 | --force-fp16] [--bf16-unet | --fp16-unet | --fp8_e4m3fn-unet | --fp8_e5m2-unet] [--fp16-vae | --fp32-vae | --bf16-vae] [--cpu-vae] [--fp8_e4m3fn-text-enc | --fp8_e5m2-text-enc | --fp16-text-enc | --fp32-text-enc] [--force-channels-last] [--directml [DIRECTML_DEVICE]] [--disable-ipex-optimize] [--preview-method [none,auto,latent2rgb,taesd]] [--preview-size PREVIEW_SIZE] [--cache-classic | --cache-lru CACHE_LRU] [--use-split-cross-attention | --use-quad-cross-attention | --use-pytorch-cross-attention] [--disable-xformers] [--force-upcast-attention | --dont-upcast-attention] [--gpu-only | --highvram | --normalvram | --lowvram | --novram | --cpu] [--reserve-vram RESERVE_VRAM] [--default-hashing-function {md5,sha1,sha256,sha512}] [--disable-smart-memory] [--deterministic] [--fast] [--dont-print-server] [--quick-test-for-ci] [--windows-standalone-build] [--disable-metadata] [--disable-all-custom-nodes] [--multi-user] [--verbose [{DEBUG,INFO,WARNING,ERROR,CRITICAL}]] [--front-end-version FRONT_END_VERSION] [--front-end-root FRONT_END_ROOT] [--user-directory USER_DIRECTORY] main.py: error: unrecognized arguments: --base-directory /basedir Requirement already satisfied: safetensors>=0.4.1 in /comfy/mnt/venv/lib/python3.10/site-packages (from transformers->-r /basedir/custom_nodes/ComfyUI-Manager/requirements.txt (line 4)) (0.5.2) Requirement already satisfied: tqdm>=4.27 in /comfy/mnt/venv/lib/python3.10/site-packages (from transformers->-r /basedir/custom_nodes/ComfyUI-Manager/requirements.txt (line 4)) (4.67.1) Requirement already satisfied: fsspec>=2023.5.0 in /comfy/mnt/venv/lib/python3.10/site-packages (from huggingface-hub>0.20->-r /basedir/custom_nodes/ComfyUI-Manager/requirements.txt (line 5)) (2025.2.0) Requirement already satisfied: click>=8.0.0 in /comfy/mnt/venv/lib/python3.10/site-packages (from typer->-r /basedir/custom_nodes/ComfyUI-Manager/requirements.txt (line 6)) (8.1.8) Requirement already satisfied: shellingham>=1.3.0 in /comfy/mnt/venv/lib/python3.10/site-packages (from typer->-r /basedir/custom_nodes/ComfyUI-Manager/requirements.txt (line 6)) (1.5.4) Requirement already satisfied: markdown-it-py>=2.2.0 in /comfy/mnt/venv/lib/python3.10/site-packages (from rich->-r /basedir/custom_nodes/ComfyUI-Manager/requirements.txt (line 7)) (3.0.0) Requirement already satisfied: pygments<3.0.0,>=2.13.0 in /comfy/mnt/venv/lib/python3.10/site-packages (from rich->-r /basedir/custom_nodes/ComfyUI-Manager/requirements.txt (line 7)) (2.19.1) Requirement already satisfied: smmap<6,>=3.0.1 in /comfy/mnt/venv/lib/python3.10/site-packages (from gitdb<5,>=4.0.1->GitPython->-r /basedir/custom_nodes/ComfyUI-Manager/requirements.txt (line 1)) (5.0.2) Requirement already satisfied: mdurl~=0.1 in /comfy/mnt/venv/lib/python3.10/site-packages (from markdown-it-py>=2.2.0->rich->-r /basedir/custom_nodes/ComfyUI-Manager/requirements.txt (line 7)) (0.1.2) Requirement already satisfied: cryptography>=3.4.0 in /comfy/mnt/venv/lib/python3.10/site-packages (from pyjwt[crypto]>=2.4.0->PyGithub->-r /basedir/custom_nodes/ComfyUI-Manager/requirements.txt (line 2)) (44.0.1) Requirement already satisfied: cffi>=1.4.1 in /comfy/mnt/venv/lib/python3.10/site-packages (from pynacl>=1.4.0->PyGithub->-r /basedir/custom_nodes/ComfyUI-Manager/requirements.txt (line 2)) (1.17.1) Requirement already satisfied: charset-normalizer<4,>=2 in /comfy/mnt/venv/lib/python3.10/site-packages (from requests~=2.22->matrix-client==0.4.0->-r /basedir/custom_nodes/ComfyUI-Manager/requirements.txt (line 3)) (3.4.1) Requirement already satisfied: idna<4,>=2.5 in /comfy/mnt/venv/lib/python3.10/site-packages (from requests~=2.22->matrix-client==0.4.0->-r /basedir/custom_nodes/ComfyUI-Manager/requirements.txt (line 3)) (3.10) Requirement already satisfied: certifi>=2017.4.17 in /comfy/mnt/venv/lib/python3.10/site-packages (from requests~=2.22->matrix-client==0.4.0->-r /basedir/custom_nodes/ComfyUI-Manager/requirements.txt (line 3)) (2025.1.31) Requirement already satisfied: wrapt<2,>=1.10 in /comfy/mnt/venv/lib/python3.10/site-packages (from Deprecated->PyGithub->-r /basedir/custom_nodes/ComfyUI-Manager/requirements.txt (line 2)) (1.17.2) Requirement already satisfied: pycparser in /comfy/mnt/venv/lib/python3.10/site-packages (from cffi>=1.4.1->pynacl>=1.4.0->PyGithub->-r /basedir/custom_nodes/ComfyUI-Manager/requirements.txt (line 2)) (2.22) == ComfyUI-Manager /comfy/mnt/ComfyUI/custom_nodes/ComfyUI-Manager/config.ini file missing, script potentially never run before. You will need to run ComfyUI-Manager a first time for the configuration file to be generated, we can not attempt to update its security level yet -- if this keeps occurring, please let the developer know so he can investigate. Thank you == Skipping ComfyUI-Manager CLI fix as we are re-using the same venv as the last execution -- If you are experiencing issues with custom nodes, use 'Manager -> Custom Nodes Manager -> Filter: Import Failed -> Try Fix' from the WebUI == Setting base_directory: /basedir ++ Logic to move content from ComfyUI directories to the new base_directory -- /comfy/mnt/ComfyUI/models not found, /basedir/models exists, skipping -- Both /comfy/mnt/ComfyUI/input (in) and /basedir/input (out) exist, skipping move. FYI attempting to list files in 'in' that are not in 'out' (empty means no differences): -- /comfy/mnt/ComfyUI/output not found, /basedir/output exists, skipping -- /comfy/mnt/ComfyUI/temp not found, /basedir/temp exists, skipping -- /comfy/mnt/ComfyUI/user not found, /basedir/user exists, skipping -- /comfy/mnt/ComfyUI/custom_nodes not found, /basedir/custom_nodes exists, skipping == Checking models directory -- /basedir/models/checkpoints already exists, skipping -- /basedir/models/loras already exists, skipping -- /basedir/models/vae already exists, skipping -- /basedir/models/configs already exists, skipping -- /basedir/models/clip_vision already exists, skipping -- /basedir/models/style_models already exists, skipping -- /basedir/models/diffusers already exists, skipping -- /basedir/models/vae_approx already exists, skipping -- /basedir/models/gligen already exists, skipping -- /basedir/models/upscale_models already exists, skipping -- /basedir/models/embeddings already exists, skipping -- /basedir/models/hypernetworks already exists, skipping -- /basedir/models/photomaker already exists, skipping -- /basedir/models/classifiers already exists, skipping !! COMFY_CMDLINE_EXTRA extended, make sure to use it in user script (if any): --base-directory /basedir == Container directory: /comfy/mnt/ComfyUI == Checking for user script: /comfy/mnt/user_script.bash =================== == Running ComfyUI -- Command line run: python3 ./main.py --listen 0.0.0.0 --disable-auto-launch --base-directory /basedir !! ERROR: ComfyUI failed or exited with an error !! Exiting script (ID: 1) ** Press ANY KEY to close this window ** Edited February 15, 20251 yr by chris smashe
February 15, 20251 yr Author 3 hours ago, chris smashe said: main.py: error: unrecognized arguments: --base-directory /basedir Hi, the error is at the beginning of your logs: "main.py: error: unrecognized arguments: --base-directory /basedir" This is due to a version of ComfyUI installed in the venv that is older than the end of January 2025 (base-directory is a very recent option) Please see https://github.com/mmartial/ComfyUI-Nvidia-Docker?tab=readme-ov-file#63-using-base_directory-with-an-outdated-comfyui for a couple of options to fix this
February 15, 20251 yr Author On 2/12/2025 at 11:43 AM, SeldomNosePicker said: First just want to say that I love this container and have been using it very frequently for a while now successfully. I run with over 20 custom nodes on my usual workflows and have great success with this container. This last update though with the basedir option I wasn't able to upgrade properly and had to start fresh, not a problem its easy for me to do this. But I ran into 2 issues this latest update, first one I've already found a workaround but want to note it. With the Mikey Nodes node (and another one I can't remember) I get an error when installing them the first time, looking at the logs though I noticed it was trying to find the comfy_extras folder located 'basedir/comfy_extras/' instead of 'mnt/ComfyUI/comfy_extras/'. I was able to fix this by copying the existing '/mnt/ComfyUI/comfy_extras/' folder here: 'basedir/comfy_extras/' and clicking 'try fix' in the Manager. Since other nodes didn't present this issue I figure this has something to do with the way that specific nodes is looking for that folder, but in-case someone else has this issue this could be a workaround. Following up 1) comfy_extras should stay within run/ComfyUI; it is is not expected to be within basedir 2) the mikey_nodes custom node is using a variable that does not work with basedir. I have proposed a PR to them that should fix it, we have to wait for them to fix it for a fully functional option. If you are willing to manually replace the python script in the custom_nodes folder, here are the details to get it working (you only need the two first changes in the file) https://github.com/bash-j/mikey_nodes/pull/45 Another option is to copy the content of comfy_extras into basedir until mikey nodes (and potential others are fixed to reflect the use of basedir Edited February 15, 20251 yr by martial
February 15, 20251 yr 2 hours ago, martial said: Hi, the error is at the beginning of your logs: "main.py: error: unrecognized arguments: --base-directory /basedir" This is due to a version of ComfyUI installed in the venv that is older than the end of January 2025 (base-directory is a very recent option) Please see https://github.com/mmartial/ComfyUI-Nvidia-Docker?tab=readme-ov-file#63-using-base_directory-with-an-outdated-comfyui for a couple of options to fix this Thanks. Im back up now.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.