Caprover restart after each app creation #1893
Comments
|
Can you get the logs and include them? |
|
sure: |
|
I don't see any restarts happening here. Looks like it was a starter successfully, then there were a few endpoint calls, some of them resulted in some errors which is totally fine. |
|
Captain is initialized Is the log that shows a successful start up. I only see one of this. |
|
I think the log are returning only the logs since the last restart... and since Caprover restarts each time a new app is created you won't see anything here. |
|
If you use docker service logs, it should return the whole logs (before restart) Alternatively, you can just add --follow to the end of the command, and create an app. This will show you the live logs. |
|
got it, here's what happens when an app is created and Caprover restarts: |
|
note that the exact same API command works fine with older version of Caprover |
|
Super helpful!
|
|
Yes, that's weird, just creating a blank app (basically just entering the name of a new app inside the UI) triggers a restart: |
|
doesn't seem to be a common issue or Github would be flooded, do you think reinstalling Caprover might fix it? |
|
1.10.1 version works perfectly btw |
|
Definitely not a common issue. It is still quite confusing. Can you try disabling your default push on your registries in the cluster tab? Does that fix the issue? |
|
I disabled the default push and that fixed the issue, thanks a lot! Not related, I see on the changelog: Improved: Added support for overriding mesh network settings and using an existing Docker Swarm 56e739c Thanks! Alex. |
|
RE: swarm 1- You can just add RE: restart on fail to push |
|
Have this same issue after creating an app, is says 
here's the logs after create of app. Note: I have docker registry setup. |
|
After disabling Default Push Registry, the creation of app now works fine. |
|
I believe this is related on this issue: when creating a one-click app, this error occurs 
|
|
@jbalatero - a few questions for you: |
|
1- what version of CapRover are you on? 2- Does it crash everytime you create a new one click app or just sometimes? It crashes everytime. Even after fresh install. After 30 seconds or so, it comes up again and works fine. 3- Are you using a self-hosted registry through CapRover or you're using a 3rd party registry like aws registry / github registry etc? |
|
|
@jbalatero - can you try enabling the self hosted registry and set that as a default registry to see the issue is reproducible? |
|
@githubsaturn I can confirm it is reproducible with that config. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
IMPORTANT: This is a bug report. If you are having problem with deploying a particular app use the deployment issue type.
What is the problem?
Since the last update, each time an app is created using the CLI/API (not tested using the caprover dashboard), Caprover restart. This revokes the API token and makes Caprover completely unusable.
If applicable, content of
captain-definitionfile:Steps to reproduce the problem:
Create a new app from a docker image from the CLI or the API.
Output of the following command on your server:
nux ams-sm5038mr-h8trf-4-3 5.15.0-84-generic #93-Ubuntu SMP Tue Sep 5 17:16:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.3 LTS
Release: 22.04
Codename: jammy
total used free shared buff/cache available
Mem: 125Gi 2.4Gi 119Gi 36Mi 3.5Gi 122Gi
Swap: 3.9Gi 0B 3.9Gi
The text was updated successfully, but these errors were encountered: