Portainer not seeing data folder?

[YouveGotMeowxy]

Before you start, we need a little bit more information from you:

Use Case (delete as appropriate): Using Portainer at Home

Have you reviewed our technical documentation and knowledge base? Yes

Question:

I ran into a Docker problem and had to uninstall, and reinstall Docker Desktop; I'm running Swarm, and had to do a re-initiate swarm, re-add 2 overlay networks, and then I could run my usual docker-compose.yml file containing my Portainer/Agent setup:

version: "3.8"

services:
  portainer:
    image: 'portainer/portainer-ee:latest'
    environment:
      TZ: 'America/Chicago'
    volumes:
      - '/opt/docker/configs/portainer/data:/data:rw'
      - '/mnt/e/Docker/Logs/portainer:/data/log:rw'
      - '/var/run/docker.sock:/var/run/docker.sock:ro'
    ports:
      - '9013:9443'
    deploy:
      #mode: 'global'
      mode: 'replicated'
      replicas: 1
      placement:
        constraints: [node.role == manager]
      restart_policy:
        condition: 'any'
    networks:
      - 'portainer'
      - 'security'

  agent:
    image: 'portainer/agent:latest'
    environment:
      AGENT_CLUSTER_ADDR: 'tasks.agent'
    volumes:
      - '/:/host:ro' # Enable 'host management features'
      - '/var/run/docker.sock:/var/run/docker.sock:ro'
    ports:
      - target: 9001
        published: 9001
        protocol: 'tcp'
        mode: 'host'
    depends_on:
      - 'portainer'
    deploy:
      mode: 'global'
      restart_policy:
        condition: 'any'
    labels:
      com.centurylinklabs.watchtower.enable: 'false'
    networks:
      - 'portainer'

networks:
  portainer:
    external: true
    name: 'portainer'
  security:
    external: true
    name: 'security'

When Portainer started, it appears to have all of my basic stuff remembered (user, environments, registries, etc.), but all of my stacks, secrets, networks, are gone. (ugh!)

Since I always used a bind mount, it appears all of the stuff in the /data folder was untouched; for example this is the /data/compose folder, and the folders all have a docker-compose.yml in them, but it seems like Portainer doesn't see them?

Is there some way to get Portainer to "see" all the stuff that's already there so that I can continue where I normally was rather than have to fight through some recovery process?

Update:

To make things even more odd, I just opened up portainer.db and looked into the "stacks" key, and can still see all my old stacks and their info there, it's just that they don't show up in the WebUI at all.

[tamarahenson]

@YouveGotMeowxy

I would like to further investigate this. Can you join our Slack Community and message me a copy of your Portainer backup?

https://join.slack.com/t/portainer/shared_invite/zt-190q9nm5v-uT0p0WFkn~K1yv2QlnHJNQ

Thanks!

[YouveGotMeowxy]

I would like to further investigate this. Can you join our Slack Community and message me a copy of your Portainer backup?

https://join.slack.com/t/portainer/shared_invite/zt-190q9nm5v-uT0p0WFkn~K1yv2QlnHJNQ

Sure thing, I can do it tomorrow. :)

By "backup" do you just mean the entire /data' folder? The 1 time I used the built-in backup tool was too long ago, and I don't have any other from the tool itself.

[tamarahenson]

@YouveGotMeowxy

Backup procedure here: https://docs.portainer.io/admin/settings#backup-portainer

Thanks!

[YouveGotMeowxy]

@tamarahenson Oop, I just made the backup and looked through it, and there's a lot of personal stuff in it (passwords, etc.), so I think I'm gonna pass on sending it over. It that the only way to solve this issue?

[YouveGotMeowxy]

It's a very longshot, but just thought I'd ask anyway; could there be a chance that portainer is somehow tied to the network's subnet/gateway, in order to load it's stacks from the settings folders?

I found in my notes that in the past I may have (don't recall offhand though) specified different subnet/gateways for my overlays, of which Portainer itself may have been in, compared to the overlay networks they're currently in.

i.e.

Previous way I created them:

docker network create --attachable --driver=overlay --scope=swarm --subnet=172.21.0.0/16 --gateway=172.21.0.1 stackname

current subnet/gateways:

[YouveGotMeowxy]

dancin with my-selfff, oh oh oh oh ....

[jamescarppe]

This is an older issue and I'm not sure if you got it resolved, but this is likely due to there being a different internal Swarm ID for your new swarm versus your old swarm. It should just be a matter of fixing this reference in the Portainer database, but as this is an older issue it may not be relevant anymore. Let us know if not and I can close the issue.