I think this is a problem in the README.md, I apologize.

In the code, if you set DISABLE_UPGRADES I skip the PREINSTALL_TORCH step.

So the README.md should have read enable DISABLE_UPGRADES after initial installation.

Can you try again please with DISABLE_UPGRADES set to false for the initial installation? (please delete the appdata installation path for a clean install)

Edited October 4, 2025Oct 4 by martial

That worked! It is launching now, and I'm able to get into the UI. Thank you!

Only other problem I had was the inability to write to the basedir folders from my Windows PC. The solution I found was to to into the Unraid GUI > Tools > New Permissions, and run that tool for the share that I created for the basedir.

2 hours ago, Ccheese4 said:

Only other problem I had was the inability to write to the basedir folders from my Windows PC. The solution I found was to to into the Unraid GUI > Tools > New Permissions, and run that tool for the share that I created for the basedir.

That is likely a Samba share issue, you have created a user on Unraid for that share but the files in basedir are owned by "99:100".

Keep in mind that files in the run folder need to stay owned by 99:100 (the default user running apps usually)

For basedir it should be fine to have alternate ownership, as long as the user can read the files.

The FORCE_CHOWN is here to try to fix that when you restart the container (and was added specifically for Unraid in that case)

Enjoy. I am not sure how much longer we will be able to support GTX series hardware, and I do not have one to test anymore.

Hello, can somebody help me how to update frontend for ComfyUI Docker? I went through docs, but I am not wiser.

I am getting this message.

Thanks.

Sadly, I do not have a magic solution for this, unless you are able to force its installation from the "Manager" while using Comfy.

My usual solution for those types of issues is to reinstall ComfyUI and the virtual environment needed to run my custom nodes (ie, a couple of re-runs with re-downloads --and using the Manager to reinstall failed nodes, which will have failed because the venv does not contain the expected content)

To do this, I recommend deleting (or renaming) the run folder in /mnt/user/appdata/comfyui-nvidia/mnt so that a new one can be created. Comfy will redownload, and after the "couple of failed nodes reinstall from the manager" step, you should be back in business.

On 10/23/2025 at 9:12 PM, ELP1 said:

Hello, can somebody help me how to update frontend for ComfyUI Docker? I went through docs, but I am not wiser.

I am getting this message.

Thanks.

Hi,

i update my frontend with the the command comfyui shows you when you start the container with an old frontend. You find the command in the container protocol. In my case the command is /comfy/mnt/venv/bin/python3 -m pip install -r /comfy/mnt/ComfyUI/requirements.txt

You can now start your container command line and just copy and paste this command. The frontend will be updaded and after a container restart you will have the new frontend.

Hey!!
Been a while since I've had a comment on this, this container has been really stable for me for a long time now so greatly appreciate that!
I am having a weird issue saving and opening workflows that I've saved in the past. When I try to save a workflow, I get an error like attached.

Then when I try to open an existing workflow, I can see the files in the webui, but clicking on it does nothing. I am able to download the existing workflows on my unraid serverfiles here '/mnt/user/appdata/comfyui-nvidia/basedir/user/default/workflows' and just upload them directly and keep working. I just dont really understand why I can't open or save workflows directly in the webui. Any thoughts? I do have set_chown to true to try and resolve but it doesn't help.

On 11/26/2025 at 8:27 AM, SeldomNosePicker said:

Hey!!
Been a while since I've had a comment on this, this container has been really stable for me for a long time now so greatly appreciate that!
I am having a weird issue saving and opening workflows that I've saved in the past. When I try to save a workflow, I get an error like attached.

Then when I try to open an existing workflow, I can see the files in the webui, but clicking on it does nothing. I am able to download the existing workflows on my unraid serverfiles here '/mnt/user/appdata/comfyui-nvidia/basedir/user/default/workflows' and just upload them directly and keep working. I just dont really understand why I can't open or save workflows directly in the webui. Any thoughts? I do have set_chown to true to try and resolve but it doesn't help.

a 405 is a "method not allowed" error, which is very weird to see.

I expect your Comfy installation is not too old, there seems to have been a similar error posted on their GH but that was March this year and the issue appears to be related to the reverse proxy is use in front of Comfy

GitHub

[Bug]: Save workflow 405(Method Not Allowed) When using N...

Frontend Version COMFYUI: v0.3.4 Expected Behavior When using a reverse proxy e.g. nginx, Save workflow should work, in previous version this issue was not there. Actual Behavior Here is the api th...

Hi Team,

A quick update:

I just released a new version of the tool Today (20251129).

I recommend you enable the USE_UV option (set to true) to really speed up package installation.

I also just released a new Community Application to use with ComfyUI Nvidia Docker.

When reviewing images, I like to see the workflows prompts to try to understand how I can improve my generations.

A month ago, Biagio announced a cool tool called "SmartGallery for ComfyUI" on Reddit

https://www.reddit.com/r/comfyui/comments/1ogrfwb/smartgallery_v130_your_comfyui_gallery_just_got/

I used it and starting integrating new features to it in PRs that Biagio has since merged.

I released a Docker container for it Today and as you can expect I added an Unraid template to use it too ;)

On 11/29/2025 at 1:57 PM, martial said:

a 405 is a "method not allowed" error, which is very weird to see.

I expect your Comfy installation is not too old, there seems to have been a similar error posted on their GH but that was March this year and the issue appears to be related to the reverse proxy is use in front of Comfy

GitHub

[Bug]: Save workflow 405(Method Not Allowed) When using N...

Frontend Version COMFYUI: v0.3.4 Expected Behavior When using a reverse proxy e.g. nginx, Save workflow should work, in previous version this issue was not there. Actual Behavior Here is the api th...

Wow that fix worked perfect thanks!

Hi everyone,

I want to run the container completely offline (no WAN access), while still being able to access the web UI locally via port mapping.

I’m using a custom Docker network with a isolated_net network:

docker network create --driver=bridge --subnet=172.20.0.0/24 --internal isolated_net

ComfyUI fails to start if the container has no internet connection.

Exits immediately with the following message:

== Testing write access as the comfy user to the run directory
== Using default behavior: Enabling upgrades (behavior depends on USE_PIPUPGRADE)
== Installing uv
  == Verify that python3 and uv are installed
  - python3: /usr/bin/python3
    version: Python 3.12.3
  -      uv: !! ERROR: subscript failed
!! Exiting script (ID: 1)

environment variables :

• DISABLE_UPGRADES=true

• USE_PIPUPGRADE=false

…the container still attempts to install or verify uv on startup, and aborts when no internet is available.

With access to the internet it starts.

Is there a way to disable the automatic uv installation/upgrade checks on startup?

Edited December 4, 2025Dec 4 by Jimmy235

ComfyUI fails to start if the container has no internet connection.

The init script logic attempts to install uv if you have USE_UV=true

Set it to USE_UV=false that should skip that part.

Given the nature of Comfy and its constant evolution, I have never considered the container as an "offline" solution.

First of all thanks a lot for this great Docker, works perfectly

I'm trying at the moment to get this custom node installed: ComfyUI-3D-Pack
However i get only error messages that torch would not be installed, see log extract below.

the thing is im running the latest version of your Docker with USE_UV set to true, so my understanding was torch is automatically installed, which i also see at the startup of confyui.

but still no luck with the installation of Comfy-3D-Pack

any advice would be appreciated.

the log shows this:

## ComfyUI-Manager: EXECUTE => ['/comfy/mnt/venv/bin/python3', '-m', 'uv', 
'pip', 'install', 'git+https://github.com/SarahWeiii/diso.git']
[!] Using Python 3.12.3 environment at: /comfy/mnt/venv
[!]    Updating https://github.com/SarahWeiii/diso.git (HEAD)
[!]     Updated https://github.com/SarahWeiii/diso.git (9792ad928ccb09bdec938779651ee03e395758a6)
[!] error: The build backend returned an error
[!]   Caused by: Call to `setuptools.build_meta:__legacy__.build_wheel` failed (exit status: 1)
[!] 
[!] [stderr]
[!] Traceback (most recent call last):
[!]   File "<string>", line 14, in <module>
[!]   File "/comfy/mnt/uv_cache/builds-v0/.tmpAM6epx/lib/python3.12/site-packages/setuptools/build_meta.py", line 331, in get_requires_for_build_wheel
[!]     return self._get_build_requires(config_settings, requirements=[])
[!]            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[!]   File "/comfy/mnt/uv_cache/builds-v0/.tmpAM6epx/lib/python3.12/site-packages/setuptools/build_meta.py", line 301, in _get_build_requires
[!]     self.run_setup()
[!]   File "/comfy/mnt/uv_cache/builds-v0/.tmpAM6epx/lib/python3.12/site-packages/setuptools/build_meta.py", line 512, in run_setup
[!]     super().run_setup(setup_script=setup_script)
[!]   File "/comfy/mnt/uv_cache/builds-v0/.tmpAM6epx/lib/python3.12/site-packages/setuptools/build_meta.py", line 317, in run_setup
[!]     exec(code, locals())
[!]   File "<string>", line 4, in <module>
[!] ModuleNotFoundError: No module named 'torch'
[!] 
[!] hint: This error likely indicates that `git` depends on `torch`, but doesn't declare it as a build dependency. If `git` is a first-party package, consider adding `torch` to its `build-system.requires`. Otherwise, either add it to your `pyproject.toml` under:
[!] 
[!] [tool.uv.extra-build-dependencies]
[!] git = ["torch"]
[!] 
[!] or `uv pip install torch` into the environment and re-run with `--no-build-isolation`.
install script failed: ComfyUI-3D-Pack
Using Python 3.12.3 environment at: /comfy/mnt/venv
Install: install script
[ComfyUI-Manager] Installation failed:
Failed to execute install script: [email protected]

[ComfyUI-Manager] Queued works are completed.
{'install': 1}

After restarting ComfyUI, please refresh the browser.

I think your problem is that the node itself depends on a 3rd party tool that needs to be compiled to work, per git+https://github.com/SarahWeiii/diso.git

and for unclear reason it does not see torch which is installed by default

That is what the userscripts_dir try to do for a few common packages.

The closest entry in there that would do the build in the SageAttention script which also does the python3 setup.py install step, but I am not sure if even with that you would encounter the same error again.

If anyone is using Traefik in front of the tool, I added a new "solved" issue about:

If you are using Traefik in front of ComfyUI or a few other services, see and use
https://www.reddit.com/r/selfhosted/comments/1ph9jio/traefik_v364_breaks_nextcloud_officecollabora/

I was unable to load or save workflows until I added the allowEncodedSlash (workflow/file.json)

Thanks for the efforts maintaining this image. Is there any plan to update to ComfyUI v0.6?

2 minutes ago, Monkey_66 said:

Thanks for the efforts maintaining this image. Is there any plan to update to ComfyUI v0.6?

Can you explain what you mean?

I do not control the updates of the Comfy core, each user has to manually update ComfyUI from the manager to update it.

My local instance is running: ComfyUI: v0.6.0-10-g36deef2c (2025-12-26)
Manager: V4.0.4

Quick note: I recently renamed the base images to follow a cuda major.minor naming convention (ie no more 3rd digit).

This only affects older CUDA releases but include 12.6.3 (ie the current latest and the default version installed if no CUDA is selected)

If you are using an older image (like 12.6.3-latest, please check that your installed image is 12.6-latest in the Repository entry of your Update Container page (might have to show advanced).

This only affects users with older installs using CUDA below 12.8 (GTX end users).

The template is updated to reflect the new naming convention, so this should not impact new installation, only already existing installations.

At the same time, I note that as the tool evolved I have added many options in the template that might be useful to most users and as such, a new installation from Community Applications might show new options

Apologies for this.

Edited December 31, 2025Dec 31 by martial

On 12/28/2025 at 4:31 PM, martial said:

Can you explain what you mean?

I do not control the updates of the Comfy core, each user has to manually update ComfyUI from the manager to update it.

My local instance is running: ComfyUI: v0.6.0-10-g36deef2c (2025-12-26)
Manager: V4.0.4

I think the issue is Comfy hasn't completed the migration to the new GitHub page yet. The https://github.com/comfy-org/ComfyUI only has version v0.1.1113 which is comfy 0.3.2 or so while the https://github.com/comfyanonymous/ComfyUI has 0.7.0, i had to install an older version of yours (docker pull mmartial/comfyui-nvidia-docker:ubuntu24_cuda13.1-20251228) before the GIT change to actually get Comfy working.

Granted for some reason Comfyui-Manager refuses to actually load properly and only shows me the custom nodes network and none of the update options.

The latest version properly loads Comfyui-manager but updating only gets you to ccomfyui 3.2 due to the git change making it unusable

3 hours ago, HaxForNox said:

I think the issue is Comfy hasn't completed the migration to the new GitHub page yet. The https://github.com/comfy-org/ComfyUI only has version v0.1.1113 which is comfy 0.3.2 or so while the https://github.com/comfyanonymous/ComfyUI has 0.7.0, i had to install an older version of yours (docker pull mmartial/comfyui-nvidia-docker:ubuntu24_cuda13.1-20251228) before the GIT change to actually get Comfy working.

Granted for some reason Comfyui-Manager refuses to actually load properly and only shows me the custom nodes network and none of the update options.

The latest version properly loads Comfyui-manager but updating only gets you to ccomfyui 3.2 due to the git change making it unusable

I got the comfyui-manager properly loading after settings "Enable Mager_Legacy_UI" To true. so besides the git repo changing its allll good

Thanks for letting me know.

I did not realize that the change was not done, they announced it as done with an official transition date ot Jan 6th.

I will not change anything given this is coming rather quickly and the changes were done to be prepared for it.

I am making a new release to go back to the old url (I see the issue on the repo being out of sync) and I have a variable ready for the transition which will just have to be turned to true to make it happen (which should be transparent)

Edited January 4Jan 4 by martial

I am making a new release with the older URL active.

Once the transition is complete it will be easy to just transition

Hi,

I have a 5070 TI and get a CUDA Error message.

I found a solution with the following commands "--disable-smart-memory --disable-cuda-malloc" but can't get it to work.

I tried inserting everything via the template, but without success.

Neither POST arguments nor a variable with CLI_ARGS worked.

Where do I find the start script in the docker container? I want to attach the parameters directly.

thank you

Sebastian

I have a 5070 TI and get a CUDA Error message.

I found a solution with the following commands "--disable-smart-memory --disable-cuda-malloc" but can't get it to work.

I tried inserting everything via the template, but without success.

Neither POST arguments nor a variable with CLI_ARGS worked.

Where do I find the start script in the docker container? I want to attach the parameters directly.

This is normal, the tool does not take arguments directly, they have to be passed through environment variables existing in the template.

If you look, you should find a COMFY_CMDLINE_EXTRA for Extra command-line options for ComfyUI; this is where you would use those command line arguments.

Hi, I found the Problem. It is the old Nvidia driver 580 in the Unraid Nvidia Plugin. Actually I can't get the version 590 to work with my 5070ti. Currently, I'm passing the GPU through to a VMware and everything works fine.