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
How to deploy image already present in the same caprover's host? No registry needed #1883
Comments
Yes! This is exactly the workaround. It's by design, since CapRover is meant to be able to pull images. Consider a case, where you have multiple nodes and you want to deploy an app that doesn't have any images on node 2. The images might get out of sync if they are local. I understand in your case, you probably have one node, but this is by design, because the architecture is designed for a multi-server environment. |
This makes perfect sense. You are right. But can I ask you to unlock this feature if there is only one node? I mean, if I use deployment method 6 and caprover detects that it's running on one node only can we have the image taken from the node and not from a registry? Caprover can now already detect the presence of a single-node cluster. This is super convenient when there are single node instances and there are more and more of them today as the servers are less and less expensive. This saves us the trouble of managing a private registry. It would be super convenient! Please. 🙏 |
What's the use case for an image that is available on the server? Even for a simple server, you still need to build the image first, right? |
Yeah. I'm building it manually. Using I have one big server with caprover and I build images there too. This way I do not need registry at all. |
Thanks for the context! I'll reopen this as a feature request. All we need to do is to ensure we check for locally available images and skip the pull caprover/src/user/ImageMaker.ts Lines 159 to 160 in cb489b2
Feel free to open a pull request anytime. |
I'm using
v1.11.0
and I'm building the image on the host where caprover runs.So if I run
docker images
:So I would like to deploy this image WITHOUT any registry.
I'm trying with deploy method 6 (or with
caprover deploy --imageName ...
) using:and the error is:
If I use deploy method 4 writing this:
it works!
Why?
I would like to use the CLI command
caprover deploy --imageName my-amazing-image/web:latest
.The text was updated successfully, but these errors were encountered: