[Bug]: Problems Accessing the Fooocus Dashboard via GitHub Actions

[Anon5698]

Checklist

• The issue has not been resolved by following the troubleshooting guide
• The issue exists on a clean installation of Fooocus
• The issue exists in the current version of Fooocus
• The issue has not been reported before recently
• The issue has been reported before but has not been fixed yet

What happened?

I am trying to open the Fooocus dashboard through a GitHub Action, but I have encountered issues. Previously, I attempted to access it via localhost on Linux, but that also failed. My inability to use Google Colab is due to limitations, and I do not have an NVIDIA GPU/driver available.

Even when I try to force Fooocus to run using the CPU, I still receive an error when running on GitHub Actions, which indicates a lack of NVIDIA support:

RuntimeError: Found no NVIDIA driver on your system. Please check that you have an NVIDIA GPU and installed a driver from http://www.nvidia.com/Download/index.aspx

Steps to reproduce the problem

Clone the Fooocus repository to your local or GitHub Actions environment.
Attempt to run the Fooocus dashboard using Docker with the command: docker run --gpus all ... (Replace with the actual command you are using.)
After that, try to access the generated URL from the Docker run, which looks like http://127.0.0.1?token=<generated_token>.
Observe that you receive an error when trying to access the URL from localhost, indicating that the server did not initialize correctly.
Attempt to run the Fooocus dashboard again using the command: python entry_with_update.py --share --always-high-vram.
Even after forcing the execution to use CPU, the error regarding the missing NVIDIA driver persists.

What should have happened?

The Fooocus dashboard should initialize successfully and allow access without any errors related to NVIDIA drivers when run in a CPU-only mode. Ideally, I should be able to access the dashboard without requiring an NVIDIA GPU, especially when configured properly for CPU execution.

What browsers do you use to access Fooocus?

Google Chrome

Where are you running Fooocus?

Locally with virtualization (e.g. Docker)

What operating system are you using?

Linux Mint

Console logs

"docker: Error response from daemon: could not select device driver "" with capabilities: [[gpu]].
ERRO[0000] error waiting for container: " / "RuntimeError: Found no NVIDIA driver on your system. Please check that you have an NVIDIA GPU and installed a driver from http://www.nvidia.com/Download/index.aspx" / "sudo docker run -p 7865:7865 -v fooocus-data:/content/data -it -e CMDARGS=--listen -e DATADIR=/content/data -e config_path=/content/data/config.txt -e config_example_path=/content/data/config_modification_tutorial.txt -e path_checkpoints=/content/data/models/checkpoints/ -e path_loras=/content/data/models/loras/ -e path_embeddings=/content/data/models/embeddings/ -e path_vae_approx=/content/data/models/vae_approx/ -e path_upscale_models=/content/data/models/upscale_models/ -e path_inpaint=/content/data/models/inpaint/ -e path_controlnet=/content/data/models/controlnet/ -e path_clip_vision=/content/data/models/clip_vision/ -e path_fooocus_expansion=/content/data/models/prompt_expansion/fooocus_expansion/ -e path_outputs=/content/app/outputs/ ghcr.io/lllyasviel/fooocus
[System ARGV] ['launch.py', '--listen']
Python 3.10.12 (main, Jul 29 2024, 16:56:48) [GCC 11.4.0]
Fooocus version: 2.5.5
Environment: config_path = /content/data/config.txt
Environment: config_example_path = /content/data/config_modification_tutorial.txt
Environment: path_checkpoints = /content/data/models/checkpoints/
Environment: path_loras = /content/data/models/loras/
Environment: path_embeddings = /content/data/models/embeddings/
Environment: path_vae_approx = /content/data/models/vae_approx/
Environment: path_upscale_models = /content/data/models/upscale_models/
Environment: path_inpaint = /content/data/models/inpaint/
Environment: path_controlnet = /content/data/models/controlnet/
Environment: path_clip_vision = /content/data/models/clip_vision/
Environment: path_fooocus_expansion = /content/data/models/prompt_expansion/fooocus_expansion/
Environment: path_outputs = /content/app/outputs/
[Cleanup] Attempting to delete content of temp dir /tmp/fooocus
[Cleanup] Cleanup successful
Traceback (most recent call last):
  File "/content/app/launch.py", line 152, in <module>
    from webui import *
  File "/content/app/webui.py", line 10, in <module>
    import modules.async_worker as worker
  File "/content/app/modules/async_worker.py", line 3, in <module>
    from extras.inpaint_mask import generate_mask_from_image, SAMOptions
  File "/content/app/extras/inpaint_mask.py", line 6, in <module>
    from extras.GroundingDINO.util.inference import default_groundingdino
  File "/content/app/extras/GroundingDINO/util/inference.py", line 3, in <module>
    import ldm_patched.modules.model_management as model_management
  File "/content/app/ldm_patched/modules/model_management.py", line 121, in <module>
    total_vram = get_total_memory(get_torch_device()) / (1024 * 1024)
  File "/content/app/ldm_patched/modules/model_management.py", line 90, in get_torch_device
    return torch.device(torch.cuda.current_device())
  File "/usr/local/lib/python3.10/dist-packages/torch/cuda/__init__.py", line 769, in current_device
    _lazy_init()
  File "/usr/local/lib/python3.10/dist-packages/torch/cuda/__init__.py", line 298, in _lazy_init
    torch._C._cuda_init()
RuntimeError: Found no NVIDIA driver on your system. Please check that you have an NVIDIA GPU and installed a driver from http://www.nvidia.com/Download/index.aspx"

Additional information

I anticipated that after running the Docker container, I would be able to access the service through the URL provided. Unfortunately, despite the configuration, the link was not available. I checked the port mapping and ensured that port 8080 was properly assigned.

Additionally, I was running Jupyter Notebook on port 9001, while the Docker container was set to listen on port 8080. Given this setup, I expected seamless interaction between the services. However, the link to access the local service returned an error, indicating that it was unreachable.

It’s important to note that I also looked into potential firewall settings and Docker logs to troubleshoot the issue. However, I was unable to pinpoint the exact cause of the failure. Any assistance you could provide in resolving this matter would be greatly appreciated.