New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[enhancement]: Publish Docker Images to a Container Registry #6318
Comments
It appears the maintainers do publish their containers to GitHub Container Registry already. 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: