Yummiii / sd-webui-forge-docker

A docker image for Stable Diffusion WebUI Forge
16 stars 9 forks source link

instead of tag "latest" could you pin it to cuda version like 12.4 etc? #8

Open fahadshery opened 6 days ago

fahadshery commented 6 days ago

Hi,

Again, thank you for making the ghcr.io/yummiii/sd-webui-forge-docker:cuda12.2...I think it's better to pin it to cuda version instead of latest?? this will help testing different cuda versions.

cheers.

Yummiii commented 6 days ago

Hii, yes it really makes more sense, I just never really got around to make it. I just published some new images with their cuda versions as their tags.

Please let me know if you ever need another image with a specific cuda version

fahadshery commented 6 days ago

thanks, I am testing your latest image now...Here are the docker logs:

docker logs -f forge-webui
Starting Stable Diffusion WebUI
Files not found, cloning...
Using Forge
Cloning into '/app/sd-webui'...
/app/sd-webui/.git: Permission denied
chmod: cannot access '/app/sd-webui/webui.sh': No such file or directory
Error: [Errno 13] Permission denied: '/app/sd-webui/venv'
/app/run.sh: line 23: ./venv/bin/activate: No such file or directory
Defaulting to user installation because normal site-packages is not writeable

why am I getting permission denies???

fahadshery commented 6 days ago

Here is where it is failing:

Building wheels for collected packages: insightface
  Building wheel for insightface (pyproject.toml): started
  Building wheel for insightface (pyproject.toml): finished with status 'done'
  Created wheel for insightface: filename=insightface-0.7.3-cp310-cp310-linux_x86_64.whl size=1055411 sha256=d7f9a34273658c245b83ed0d75f3c0617e45eb407d7ee6f9f6c0273a48b74f61
  Stored in directory: /home/webui/.cache/pip/wheels/e3/d0/80/e3773fb8b6d1cca87ea1d33d9b1f20a223a6493c896da249b5
Successfully built insightface
Installing collected packages: wcwidth, easydict, urllib3, typing-extensions, tqdm, threadpoolctl, six, PyYAML, pyparsing, protobuf, prettytable, Pillow, packaging, numpy, networkx, kiwisolver, joblib, idna, fonttools, eval-type-backport, cython, cycler, charset-normalizer, certifi, annotated-types, tifffile, scipy, requests, python-dateutil, pydantic-core, opencv-python-headless, onnx, lazy-loader, imageio, contourpy, scikit-learn, scikit-image, pydantic, matplotlib, albucore, albumentations, insightface
  WARNING: The script tqdm is installed in '/home/webui/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
  WARNING: The scripts f2py and numpy-config are installed in '/home/webui/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
  WARNING: The scripts fonttools, pyftmerge, pyftsubset and ttx are installed in '/home/webui/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
  WARNING: The scripts cygdb, cython and cythonize are installed in '/home/webui/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
  WARNING: The script normalizer is installed in '/home/webui/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
  WARNING: The scripts lsm2bin, tiff2fsspec, tiffcomment and tifffile are installed in '/home/webui/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
  WARNING: The scripts backend-test-tools, check-model and check-node are installed in '/home/webui/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
  WARNING: The scripts imageio_download_bin and imageio_remove_bin are installed in '/home/webui/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
  WARNING: The script insightface-cli is installed in '/home/webui/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
Successfully installed Pillow-10.4.0 PyYAML-6.0.2 albucore-0.0.17 albumentations-1.4.16 annotated-types-0.7.0 certifi-2024.8.30 charset-normalizer-3.3.2 contourpy-1.3.0 cycler-0.12.1 cython-3.0.11 easydict-1.13 eval-type-backport-0.2.0 fonttools-4.54.1 idna-3.10 imageio-2.35.1 insightface-0.7.3 joblib-1.4.2 kiwisolver-1.4.7 lazy-loader-0.4 matplotlib-3.9.2 networkx-3.3 numpy-2.1.1 onnx-1.16.2 opencv-python-headless-4.10.0.84 packaging-24.1 prettytable-3.11.0 protobuf-5.28.2 pydantic-2.9.2 pydantic-core-2.23.4 pyparsing-3.1.4 python-dateutil-2.9.0.post0 requests-2.32.3 scikit-image-0.24.0 scikit-learn-1.5.2 scipy-1.14.1 six-1.16.0 threadpoolctl-3.5.0 tifffile-2024.9.20 tqdm-4.66.5 typing-extensions-4.12.2 urllib3-2.2.3 wcwidth-0.2.13
/app/run.sh: line 25: deactivate: command not found
/app/run.sh: line 27: /app/sd-webui/webui.sh: No such file or directory

I just cloned your repo... Here is my docker compose:

services:
  forge-webui:
    image: ghcr.io/yummiii/sd-webui-forge-docker:latest
    container_name: forge-webui
    environment:
      - PUID=${PUID:-1000}
      - PGID=${PGID:-1000}
      - "ARGS=--listen --enable-insecure-extension-acces"
      - "UI=forge"
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /etc/timezone:/etc/timezone:ro
      - "./data:/app/sd-webui"
    deploy:
      resources:
        reservations:
          devices:
          - driver: nvidia
            count: all
            capabilities: [gpu]
    restart: unless-stopped
Yummiii commented 5 days ago

Did you create the ./data folder? I've seen this happen when you don't and let docker create it. I'm assuming you're on Linux

fahadshery commented 5 days ago

Did you create the ./data folder? I've seen this happen when you don't and let docker create it. I'm assuming you're on Linux

yes, I did.

but when I don't all went fine! thanks for your help... I still suggest you publish separate images for separate cuda drivers. Makes it super easy! Many thanks for your hardwork...