portainer: After server reboot, Portainer is unable to find containers/load dashboard data

Description

Steps to reproduce the issue:

  1. Install Portainer
  2. Reboot server

Any other info e.g. Why do you consider this to be a bug? What did you expect to happen instead?

Technical details:

  • Portainer version: 1.11.0
  • Portainer Docker image tag (latest/arm/windows…): latest
  • Target Docker version (the host/cluster you manage):
  • Target Swarm version (if applicable):
  • Platform (windows/linux): CentOS 7
  • Browser:

Even after re-running the Portainer docker from scratch, I get a “FAILURE: unable to load dashboard data” message when logging in.

I can see all my containers still running via docker ps, but Portainer does not show them.

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Reactions: 3
  • Comments: 18 (5 by maintainers)

Commits related to this issue

Most upvoted comments

If you want portainer to restart automatically and to persist it’s data on your disk to /opt/portainer-data for example, use the following command:

docker run -d -p 9000:9000 --restart always --name portainer -v /opt/portainer-data:/data -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer 

Yes, you need to start portainer and bind mount the docker socket for the ‘manage local endpoint’ option to work.

E.g. docker run -d -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer

docker run -d -p 9000:9000 --restart always --name portainer -v /opt/portainer-data:/data -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer

Works like a charm on archlinux remote server. Thanks!

docker run -d -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer

this will work for portainer UI.