You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On release, publish the built docker image to a publicly accessible container registry. This can be accomplished quite easily in a GitHub action and published to the GitHub container registry. Alternatively, There are some GitHub actions that make it easy to publish to Docker Hub with API keys as GitHub secrets.
Alternatives
Currently, users have to clone this repository and build the images themselves, which is significantly more effort than just being able to docker image pull ....
Additional Content
Published images make it easier for people to just give InvokeAI a quick try with minimal effort.
The text was updated successfully, but these errors were encountered:
To the maintainers - please can you enable users to see in GitHub these without digging through the build logs. You can do this by clicking the cog icon in the "About" section of the repo and enabling "Packages".
Seconded. I would love to put InvokeAI, LocalAI and AnythingLLM into one finite compose deployment. Allows for smooth updating of the core applications and is a great and easy method to do this stuff.
Is there an existing issue for this?
Contact Details
No response
What should this feature add?
On release, publish the built docker image to a publicly accessible container registry. This can be accomplished quite easily in a GitHub action and published to the GitHub container registry. Alternatively, There are some GitHub actions that make it easy to publish to Docker Hub with API keys as GitHub secrets.
Alternatives
Currently, users have to clone this repository and build the images themselves, which is significantly more effort than just being able to
docker image pull ...
.Additional Content
Published images make it easier for people to just give InvokeAI a quick try with minimal effort.
The text was updated successfully, but these errors were encountered: