This repository primarily provides a Gradio GUI for Kohya's Stable Diffusion trainers. However, support for Linux OS is also offered through community contributions. macOS support is not optimal at the moment but might work if the conditions are favorable.

The GUI allows you to set the training parameters and generate and run the required CLI commands to train the model.

• Kohya's GUI
  • Table of Contents
  • 🦒 Colab
  • Installation
    • Windows
      • Windows Pre-requirements
      • Setup Windows
      • Optional: CUDNN 8.9.6.50
    • Linux and macOS
      • Linux Pre-requirements
      • Setup Linux
      • Install Location
    • Runpod
      • Manual installation
      • Pre-built Runpod template
    • Docker
      • Get your Docker ready for GPU support
        • Windows
        • Linux, OSX
      • Design of our Dockerfile
      • Use the pre-built Docker image
      • Local docker build
      • ashleykleynhans runpod docker builds
  • Upgrading
    • Windows Upgrade
    • Linux and macOS Upgrade
  • Starting GUI Service
    • Launching the GUI on Windows
    • Launching the GUI on Linux and macOS
  • Custom Path Defaults
  • LoRA
  • Sample image generation during training
  • Troubleshooting
    • Page File Limit
    • No module called tkinter
    • LORA Training on TESLA V100 - GPU Utilization Issue
      • Issue Summary
      • Potential Solutions
  • SDXL training
  • Masked loss
  • Change History
    • v24.1.0

This Colab notebook was not created or maintained by me; however, it appears to function effectively. The source can be found at: https://github.com/camenduru/kohya_ss-colab.

I would like to express my gratitude to camendutu for their valuable contribution. If you encounter any issues with the Colab notebook, please report them on their repository.

Colab	Info
	kohya_ss_gui_colab

To install the necessary dependencies on a Windows system, follow these steps:

1. Install Python 3.10.11.

   • During the installation process, ensure that you select the option to add Python to the 'PATH' environment variable.

2. Install CUDA 11.8 toolkit.

3. Install Git.

4. Install the Visual Studio 2015, 2017, 2019, and 2022 redistributable.

To set up the project, follow these steps:

1. Open a terminal and navigate to the desired installation directory.

2. Clone the repository by running the following command:

   git clone --recursive https://github.com/bmaltais/kohya_ss.git

3. Change into the kohya_ss directory:

   cd kohya_ss

4. Run one of the following setup script by executing the following command:

   For systems with only python 3.10.11 installed:

   .\setup.bat

   For systems with only more than one python release installed:

   .\setup-3.10.bat

   During the accelerate config step, use the default values as proposed during the configuration unless you know your hardware demands otherwise. The amount of VRAM on your GPU does not impact the values used.

The following steps are optional but will improve the learning speed for owners of NVIDIA 30X0/40X0 GPUs. These steps enable larger training batch sizes and faster training speeds.

1. Run .\setup.bat and select 2. (Optional) Install cudnn files (if you want to use the latest supported cudnn version).

To install the necessary dependencies on a Linux system, ensure that you fulfill the following requirements:

• Ensure that venv support is pre-installed. You can install it on Ubuntu 22.04 using the command:

  apt install python3.10-venv

• Install the CUDA 11.8 Toolkit by following the instructions provided in this link.

• Make sure you have Python version 3.10.9 or higher (but lower than 3.11.0) installed on your system.

To set up the project on Linux or macOS, perform the following steps:

1. Open a terminal and navigate to the desired installation directory.

2. Clone the repository by running the following command:

   git clone --recursive https://github.com/bmaltais/kohya_ss.git

3. Change into the kohya_ss directory:

   cd kohya_ss

4. If you encounter permission issues, make the setup.sh script executable by running the following command:

   chmod +x ./setup.sh

5. Run the setup script by executing the following command:

   ./setup.sh

   Note: If you need additional options or information about the runpod environment, you can use setup.sh -h or setup.sh --help to display the help message.

The default installation location on Linux is the directory where the script is located. If a previous installation is detected in that location, the setup will proceed there. Otherwise, the installation will fall back to /opt/kohya_ss. If /opt is not writable, the fallback location will be $HOME/kohya_ss. Finally, if none of the previous options are viable, the installation will be performed in the current directory.

For macOS and other non-Linux systems, the installation process will attempt to detect the previous installation directory based on where the script is run. If a previous installation is not found, the default location will be $HOME/kohya_ss. You can override this behavior by specifying a custom installation directory using the -d or --dir option when running the setup script.

If you choose to use the interactive mode, the default values for the accelerate configuration screen will be "This machine," "None," and "No" for the remaining questions. These default answers are the same as the Windows installation.

To install the necessary components for Runpod and run kohya_ss, follow these steps:

1. Select the Runpod pytorch 2.0.1 template. This is important. Other templates may not work.

2. SSH into the Runpod.

3. Clone the repository by running the following command:

   cd /workspace
   git clone --recursive https://github.com/bmaltais/kohya_ss.git

4. Run the setup script:

   cd kohya_ss
   ./setup-runpod.sh

5. Run the GUI with:

   ./gui.sh --share --headless

   or with this if you expose 7860 directly via the runpod configuration:

   ./gui.sh --listen=0.0.0.0 --headless

6. Connect to the public URL displayed after the installation process is completed.

To run from a pre-built Runpod template, you can:

1. Open the Runpod template by clicking on https://runpod.io/gsc?template=ya6013lj5a&ref=w18gds2n.

2. Deploy the template on the desired host.

3. Once deployed, connect to the Runpod on HTTP 3010 to access the kohya_ss GUI. You can also connect to auto1111 on HTTP 3000.

Once you have installed Docker Desktop, CUDA Toolkit, NVIDIA Windows Driver, and ensured that your Docker is running with WSL2, you are ready to go.

Here is the official documentation for further reference.
https://docs.nvidia.com/cuda/wsl-user-guide/index.html#nvidia-compute-software-support-on-wsl-2 https://docs.docker.com/desktop/wsl/use-wsl/#gpu-support

Install an NVIDIA GPU Driver if you do not already have one installed.
https://docs.nvidia.com/datacenter/tesla/tesla-installation-notes/index.html

Install the NVIDIA Container Toolkit with this guide.
https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html

• It is required that all training data is stored in the dataset subdirectory, which is mounted into the container at /dataset.
• Please note that the file picker functionality is not available. Instead, you will need to manually input the folder path and configuration file path.
• TensorBoard has been separated from the project.
  • TensorBoard is not included in the Docker image.
  • The "Start TensorBoard" button has been hidden.
  • TensorBoard is launched from a distinct container as shown here.
• The browser won't be launched automatically. You will need to manually open the browser and navigate to http://localhost:7860/ and http://localhost:6006/
• This Dockerfile has been designed to be easily disposable. You can discard the container at any time and restart it with the new code version.

git clone --recursive https://github.com/bmaltais/kohya_ss.git
cd kohya_ss
docker compose up -d

To update the system, do docker compose down && docker compose up -d --pull always

git clone --recursive https://github.com/bmaltais/kohya_ss.git
cd kohya_ss
docker compose up -d --build

To update the system, checkout to the new code version and rebuild using docker compose down && docker compose up -d --build --pull always

If you are running on Linux, an alternative Docker container port with fewer limitations is available here.

You may want to use the following repositories when running on runpod:

• Standalone Kohya_ss template: https://github.com/ashleykleynhans/kohya-docker
• Auto1111 + Kohya_ss GUI template: https://github.com/ashleykleynhans/stable-diffusion-docker

To upgrade your installation to a new version, follow the instructions below.

If a new release becomes available, you can upgrade your repository by running the following commands from the root directory of the project:

1. Pull the latest changes from the repository:

   git pull

2. Run the setup script:

   .\setup.bat

To upgrade your installation on Linux or macOS, follow these steps:

1. Open a terminal and navigate to the root directory of the project.

2. Pull the latest changes from the repository:

   git pull

3. Refresh and update everything:

   ./setup.sh

To launch the GUI service, you can use the provided scripts or run the kohya_gui.py script directly. Use the command line arguments listed below to configure the underlying service.

--listen: Specify the IP address to listen on for connections to Gradio.
--username: Set a username for authentication.
--password: Set a password for authentication.
--server_port: Define the port to run the server listener on.
--inbrowser: Open the Gradio UI in a web browser.
--share: Share the Gradio UI.
--language: Set custom language

On Windows, you can use either the gui.ps1 or gui.bat script located in the root directory. Choose the script that suits your preference and run it in a terminal, providing the desired command line arguments. Here's an example:

gui.ps1 --listen 127.0.0.1 --server_port 7860 --inbrowser --share

or

gui.bat --listen 127.0.0.1 --server_port 7860 --inbrowser --share

To launch the GUI on Linux or macOS, run the gui.sh script located in the root directory. Provide the desired command line arguments as follows:

gui.sh --listen 127.0.0.1 --server_port 7860 --inbrowser --share

The repository now provides a default configuration file named config.toml. This file is a template that you can customize to suit your needs.

To use the default configuration file, follow these steps:

1. Copy the config example.toml file from the root directory of the repository to config.toml.
2. Open the config.toml file in a text editor.
3. Modify the paths and settings as per your requirements.

This approach allows you to easily adjust the configuration to suit your specific needs to open the desired default folders for each type of folder/file input supported in the GUI.

You can specify the path to your config.toml (or any other name you like) when running the GUI. For instance: ./gui.bat --config c:\my_config.toml

To train a LoRA, you can currently use the train_network.py code. You can create a LoRA network by using the all-in-one GUI.

Once you have created the LoRA network, you can generate images using auto1111 by installing this extension.

A prompt file might look like this, for example:

# prompt 1
masterpiece, best quality, (1girl), in white shirts, upper body, looking at viewer, simple background --n low quality, worst quality, bad anatomy, bad composition, poor, low effort --w 768 --h 768 --d 1 --l 7.5 --s 28

# prompt 2
masterpiece, best quality, 1boy, in business suit, standing at street, looking back --n (low quality, worst quality), bad anatomy, bad composition, poor, low effort --w 576 --h 832 --d 2 --l 5.5 --s 40

Lines beginning with # are comments. You can specify options for the generated image with options like --n after the prompt. The following options can be used:

• --n: Negative prompt up to the next option.
• --w: Specifies the width of the generated image.
• --h: Specifies the height of the generated image.
• --d: Specifies the seed of the generated image.
• --l: Specifies the CFG scale of the generated image.
• --s: Specifies the number of steps in the generation.

The prompt weighting such as ( ) and [ ] is working.

If you encounter any issues, refer to the troubleshooting steps below.

If you encounter an X error related to the page file, you may need to increase the page file size limit in Windows.

If you encounter an error indicating that the module tkinter is not found, try reinstalling Python 3.10 on your system.

When training LORA on a TESLA V100, users reported low GPU utilization. Additionally, there was difficulty in specifying GPUs other than the default for training.

• GPU Selection: Users can specify GPU IDs in the setup configuration to select the desired GPUs for training.
• Improving GPU Load: Utilizing adamW8bit optimizer and increasing the batch size can help achieve 70-80% GPU utilization without exceeding GPU memory limits.

The documentation in this section will be moved to a separate document later.

The masked loss is supported in each training script. To enable the masked loss, specify the --masked_loss option.

The feature is not fully tested, so there may be bugs. If you find any issues, please open an Issue.

ControlNet dataset is used to specify the mask. The mask images should be the RGB images. The pixel value 255 in R channel is treated as the mask (the loss is calculated only for the pixels with the mask), and 0 is treated as the non-mask. The pixel values 0-255 are converted to 0-1 (i.e., the pixel value 128 is treated as the half weight of the loss). See details for the dataset specification in the LLLite documentation.

• To ensure cross-platform compatibility and security, the GUI now defaults to using "shell=False" when running subprocesses. This is based on documentation and should not cause issues on most platforms. However, some users have reported issues on specific platforms such as runpod and colab. PLease open an issue if you encounter any issues.
• Add support for custom LyCORIS toml config files. Simply type the path to the config file in the LyCORIS preset dropdown.
• Improve files and folders validation
• Added a new setup-3.10.bat file to set the venv to specifically use python 3.10.x instead of the default python the system might use.
• Relocate toml training config file to same folder as the model output directory.