Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should be considered a WIP, but it's an attempt at InvokeAI's v3.0 integration into the current workflow. It will need to be reviewed for conformity with @AbdBarho's standards for this repo, but I tried to symlink in directories in a way that conforms with existing structure. There may be better ways to do this, such as disabling automatic downloads and copying files around, but this is the best I could do for now, perhaps it will be useful as a starting point. It is entirely functional for me.
The Dockerfile here is based on the upstream InvokeAI's Dockerfile.
The main changes consist of pulling in the invoke repo instead of building from it, as well as symlinks to their proper place. CPU support (as you do with A1111) is easily added if docker-compose from this repo is modified to pass GPU_DRIVER.
Due to the way InvokeAI runs, it will download some "core" models and support files while providing very little debugging output. First run took over an hour of downloading upscale models and other supporting files.
Closes issue #555 #553
Update versions