https://github.com/cpnxp/easy-diffusion-dockerfile
An unoffical Dockerfile for easy-diffusion
https://github.com/cpnxp/easy-diffusion-dockerfile
dockerfile easy-diffusion stable-diffusion
Last synced: 12 months ago
JSON representation
An unoffical Dockerfile for easy-diffusion
- Host: GitHub
- URL: https://github.com/cpnxp/easy-diffusion-dockerfile
- Owner: cpnxp
- License: mit
- Created: 2025-02-08T15:44:21.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2025-02-08T16:28:16.000Z (about 1 year ago)
- Last Synced: 2025-02-08T17:26:35.085Z (about 1 year ago)
- Topics: dockerfile, easy-diffusion, stable-diffusion
- Language: Dockerfile
- Homepage:
- Size: 2.93 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Easy-Diffusion-Dockerfile
Dockerfile for Easy-Diffusion with volume support for models, output and config backup
This is just the containerization of Easy-Diffusion please see: https://github.com/easydiffusion/easydiffusion for the original project.
I am not affiliated with Easy-Diffusion
I created this container so I could have all of my AI workloads running containerized in my homelab.
## Requirements
You need to have your docker environment setup for GPU use.
## Building
From inside the git project run the following command
```shell
docker build -t your/taghere .
```
## Usage
Deploy the container using a command similar to this one, I have not pushed this to docker hub
```shell
docker run -d -v ed-models:/opt/easy-diffusion/models -v ed-config:/opt/easy-diffusion/config-backup -v ed-output:/opt/easy-diffusion/output -p 9000:9000 --gpus=all --name easy-diffusion --restart always your/taghere
```
You can customize the config.yaml for your use before building the container or pre-populate the ed-config volume with your config.yaml
Due to the way the installer / start.sh works, stopping and restarting the container will trigger a check for updates so be aware
the app may update within the container on a container restart. This shouldn't pose any issues unless the installer process changes.