Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unable to retrieve volumes #11842

Open
2 tasks done
joshoram80 opened this issue May 18, 2024 · 3 comments
Open
2 tasks done

Unable to retrieve volumes #11842

joshoram80 opened this issue May 18, 2024 · 3 comments
Labels
bug/need-confirmation kind/bug Applied to Bugs

Comments

@joshoram80
Copy link

Before you start please confirm the following.

Problem Description

It has been a while since I have looked at my Portainer instance, but now I am seeing an error that I have not encountered before.

The Dashboard and Volumes pages are empty, and I get the error "Unable to retrieve volumes"

I have Portainer running in Docker and served via Caddy reverse proxy. Auth is through LDAP

Expected Behavior

Dashboard and Volumes tab displays docker volumes.

Actual Behavior

Error is thrown and pages are empty

Steps to Reproduce

Spin up Portainer container
Log in
Go to dashboard or volumes Tab

Portainer logs or screenshots

2024/05/18 08:29AM WRN github.com/portainer/portainer/api/docker/snapshot.go:80 > unable to snapshot volumes | error="Error response from daemon: <html><body><h1>403 Forbidden</h1>\nRequest forbidden by administrative rules.\n</body></html>" environment=primary

Portainer version

2.19.5

Portainer Edition

Community Edition (CE)

Platform and Version

Docker 25.0.2

OS and Architecture

Ubuntu 22.04 x64

Browser

Vivaldi

What command did you use to deploy Portainer?

#### Portainer - WebUI for Containers
  portainer:
    <<: *common-keys-core
    container_name: portainer
    image: portainer/portainer-ce:latest
    command: -H unix:///var/run/docker.sock # # Use Docker Socket Proxy instead for improved security
    #command: -H tcp://socket-proxy:2375
    networks:
      - caddy
      - socket
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro # # Use Docker Socket Proxy instead for improved security
      - $DOCKERDIR/appdata/portainer/data:/data # Change to local directory if you want to save/transfer config locally
    environment:
      - TZ=$TZ
    labels:
      - caddy=portainer.$DOMAINNAME
      - caddy.0_import=tls
      - caddy.1_import=auth
      - caddy.reverse_proxy={{upstreams 9000}}

Additional Information

No response
@jonisapp
Copy link

I also have this bug and I am also using caddy-docker-proxy. Since volumes are correctly listed by docker and Portainer's other features seem to be working, it would be interesting to know what Portainer needs to display volumes. Certain http headers or particular webdocket configuration? I have to admit that I'm not sure where to look for this problem, so if anyone has any useful information, I'd love to hear from you!

@joshoram80
Copy link
Author

joshoram80 commented Jun 12, 2024 •
edited

The issue for me was solved by adding VOLUMES=1 to the envvars for Docker Socket Proxy which I never had to do before.

@jonisapp
Copy link

The issue for me was solved by adding VOLUMES=1 to the envvars for Docker Socket Proxy which I never had to do before.

So in this case I have the same problem maybe for a different reason because I'm not using docker-socket-proxy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug/need-confirmation kind/bug Applied to Bugs
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@joshoram80 @jonisapp