[Deployment Issue] Restart caprover after update failure about caprover HOT 12 CLOSED

You have a system failure (disk failure). Definitely your old password does not work. But if you're lucky enough, you can get the dashboard up and running

Step 1- clean up your swarm:

docker swarm leave --force

Step 2- install CapRover using the installation command (NOT docker service create)
https://caprover.com/docs/get-started.html#step-1-caprover-installation

from caprover.

Hello thanks for the help, I'm stuck here after running your command and this:

docker run -p 80:80 -p 443:443 -p 3000:3000 -e ACCEPTED_TERMS=true -v /var/run/docker.sock:/var/run/docker.sock -v /captain:/captain caprover/caprover

Captain Starting ...
Installing Captain Service ...
     
 Installation of CapRover is starting...     
For troubleshooting, please see: https://caprover.com/docs/troubleshooting.html
     
     


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0x7624f6bc

from caprover.

Your docker image and/or docker installation is corrupted. Try running this:

docker image rm caprover/caprover
docker pull caprover/caprover
docker run -p 80:80 -p 443:443 -p 3000:3000 -e ACCEPTED_TERMS=true -v /var/run/docker.sock:/var/run/docker.sock -v /captain:/captain caprover/caprover

If this doesn't work, your host disk is corrupted.

from caprover.

Still the same, however, I don't think it's downloading the image again but it looks like it's using the cached image.
Should I run this to clear the cache? Would this remove my other cached images which also have relevant data for me?

docker system prune -a

from caprover.

If you run this, all images will be pruned (including your apps). Run docker images | grep caprover and remove all images that you see. Do this until docker images | grep caprover doesn't return anything

from caprover.

I think you were missing this command after removing the caprover images:

docker image prune

But the output is still the same :(. I've tried to run the docker image with -it --entrypoint sh to verify that code files were there and they seem to be there.
Other detail: I'm running on rpi 3b.

If helpful, this runs fine and I don't think other docker images are compromised:

docker run hello-world

from caprover.

I have some more interesting news, after building the image from repo (to make sure it was not something dealing with docker's cache) and starting it in the same way as the docs, I have the same issue:

docker run -p 80:80 -p 443:443 -p 3000:3000 -e ACCEPTED_TERMS=true -v /var/run/docker.sock:/var/run/docker.sock -v /captain:/captain caprover/caprover-custom

from caprover.

By running that line it's only the installer that is using the custom image. CapRover internally sets up the docker service using the official image referenced here:

from caprover.

After tagging the image with caprover/caprover I still have the same result. I don't think it's using the cached image from docker at this point?

docker images | grep caprover
caprover/caprover-custom                            latest               3a61961f0e9c   11 hours ago     641MB
caprover/caprover                                   latest               3a61961f0e9c   11 hours ago     641MB

docker run -p 80:80 -p 443:443 -p 3000:3000 -e ACCEPTED_TERMS=true -v /var/run/docker.sock:/var/run/docker.sock -v /captain:/captain caprover/caprover
Captain Starting ...
Installing Captain Service ...


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0x7494869c
     
 Installation of CapRover is starting...     
For troubleshooting, please see: https://caprover.com/docs/troubleshooting.html

from caprover.

This must be a docker or a host issue.

Can you reproduce this on a brand new server?

from caprover.

I can try, but it will take a while because I have lots of configurations to transfer. Anyway, I tried with a docker re-install and we are still at the same point :/.

from caprover.

Hello,
I've finally found a workaround. The issue is probably related to a system kibrary upgrade which has conflicts with npm:
https://www.reddit.com/r/homebridge/comments/v3b851/getting_fatal_error_in_line_0_failuremessage/
https://blog.samcater.com/fix-workaround-rpi4-docker-libseccomp2-docker-20/ (installing libseccomp2 solved the issue)
https://jackstromberg.com/2021/07/how-to-add-buster-backports-to-a-raspberry-pi/

Thanks a lot for the help.

from caprover.