CapRover has residual state (especially when performing operations via Docker cli)
Author: bestonyCreated Apr 13, 2026Updated Apr 19, 2026
What is the problem?
CapRover has residual state (especially when performing operations via Docker cli), and due to this residual state, when users open the CapRover web page, some containers continuously request Docker Swarm to find containers, causing the CPU usage of Docker Swarm to persistently increase.
Steps to reproduce the problem:
- create app on docker
- use docker cli to control your service / app;
- restart docker;
- go to CapRover Panel, and Go To Log Panel. (sometimes log will fetch failed)
if you log fetch failed, you will see your Server's CPU will be high to 100%
Output of the following command on your server:
root@server:~# uname -a && lsb_release -a && free -h
Linux codex-car 6.8.0-107-generic #107-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 13 19:51:50 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 24.04.4 LTS
Release: 24.04
Codename: noble
total used free shared buff/cache available
Mem: 15Gi 2.1Gi 10Gi 16Mi 3.7Gi 13Gi
Swap: 0B 0B 0BLog File of Docker Engine
Source: caprover/caprover