Updating one-click-apps when template build docker container? #1963
-
Hello, Still wrapping my head around how CapRover does updates in some instances. In the below template file, the Pocketbase container is built using a Dockerfile. If you used this template to install Pocketbase, how would you update it to a newer version later? There's no Docker Hub image to reference? I assume you'd use method 4 or 5 and adapt the template to an actual Dockerfile or captain-definition? Which is easy enough but seems annoying to do for every update? Am I missing something or is the better solution (in this specific case) to update the template to use a prebuilt image? Thanks!
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
You're 100% correct. Dockerfile lines are generally annoying to update. And there are two reasons why they are used:
For this second issue, there is really nothing that we can do on CapRover to prevent this issue. |
Beta Was this translation helpful? Give feedback.
You're 100% correct.
Dockerfile lines are generally annoying to update. And there are two reasons why they are used:
To override
CMD
CapRover doesn't currently read the
command
line in the template, so if a template needs to override that, the only way is to use Dockerfile lines. This is due to the fact that Docker doesn't offer docker compose in their APIs. So we have to fake a docker-compose parser to convert docker-compose syntax to Docker API. It's definitely a highly used flag, so PRs are definitely welcomed!To support apps that don't offer docker images
Pockerbase is an example. Here is an open thread: pocketbase/pocketbase#92
It's actually quite simple to set this up, I'm not …