Portainer local environment disconnected after Hyper-V CPU/RAM increase and VM reboot

[jsharma-main]

Ask a Question!

Hello,
I am facing an issue with Portainer CE running in Docker Swarm after increasing CPU and RAM on a Hyper-V VM and rebooting the server.
Environment:
• Hyper-V VM
• Ubuntu/Linux
• Docker Swarm (3 nodes)
• Portainer CE deployed as swarm service
• Portainer version: 2.33.3
• Docker manager version: 29.1.3
• Worker nodes: 25.0.14m1
Issue:
After increasing CPU/RAM on the Hyper-V VM and rebooting:
• Portainer login page works
• Admin login works
• But the local environment shows:
o Disconnected
o The environment named local is unreachable
Docker itself appears healthy.
Checks already performed:
• systemctl status docker → active/running
• docker ps → containers healthy
• docker node ls → swarm healthy
• /var/run/docker.sock exists and permissions look correct
• Disk space and memory are fine
• Time synchronization is fine
Portainer logs show:
failed opening store | error=timeout
There were also multiple failed Portainer swarm task restarts immediately after reboot.
I already tested:
docker service update --force infra_portainer
and also:
docker service scale infra_portainer=0
docker service scale infra_portainer=1
Portainer container recreates successfully each time, but:
• the environment remains disconnected
• the “Add Environment” button is also missing from UI
It currently looks like Docker/Swarm are healthy, but Portainer internal DB/environment metadata may have become inconsistent after reboot.
Questions:

1. Is this likely BoltDB corruption or endpoint metadata corruption?
2. Is renaming/removing portainer.db the recommended recovery method here?
3. Is there a safer way to rebuild only the environment state without resetting Portainer completely?
4. Has anyone seen this after Hyper-V hardware changes or abrupt swarm task restarts?
   Thanks.