Portainer states its offline

[huzzyz]

I've tried just about everything, recreating the containers, starting from scratch. I have no idea why the status light appears offline. The widget below displays my running containers but above that it stays offline.

- Portainer:
    icon: portainer.png
    href: http://192.168.1.53:9000
    description: Docker Maintenance
    container: portainer
    widget:
     type: portainer
     url: http://192.168.1.53:9000
     env: 2
     key: REDACTED

[benphelps]

You'll need to pass the docker server it's on as well, as defined in your docker.yaml file.

[huzzyz]

Sorry, done that too.

    - Portainer:
        icon: portainer.png
        href: http://192.168.1.53:9000
        description: Docker Maintenance
        container: portainer
        server: my-local-docker
        widget:
         type: portainer
         url: http://192.168.1.53:9000
         env: 2
         key: REDACTED

my-local-docker:
  socket: /var/run/docker.sock

[benphelps]

Make sure you're passing the docker socket through to your homepage container, as shown in the wiki: https://github.com/benphelps/homepage/wiki/Docker-Integration#configuration

[huzzyz]

Already have.

[colutti]

Same thing here.

This is from the services file:

From my docker-compose:

My docker.yaml:

The results:

[C8opmBM]

I am having the exact issue on all containers (Status offline)

  homepage:
    <<: *internalbase
    image: ghcr.io/benphelps/homepage:latest
    user: 1001:100 # Optional, change to your user and group IDs for permissions
    volumes:
      - /srv/dev-disk-by-label-downloads/mediatools/homepage:/app/config
      - /srv/dev-disk-by-label-downloads/mediatools/homepage/icons:/app/public/icons
      - /srv/dev-disk-by-label-downloads/mediatools/homepage/images:/app/public/images
      - /srv/dev-disk-by-label-Media:/hdd1
      - /srv/dev-disk-by-label-Media2:/hdd2
      - /var/run/docker.sock:/var/run/docker.sock # This passes your local docker socket to the container
    ports:
      - 3000:3000
    container_name: homepage

# For configuration options and examples, please see:
# https://github.com/benphelps/homepage/wiki/Docker-Integration

#my-docker:
#  host: 127.0.0.1
#  port: 2375

#other-docker:
#  socket: /var/run/docker.sock

local:
  socket: /var/run/docker.sock

- Utilities:
    - Media Portainer:
        icon: portainer.png
        href: http://192.168.1.151:9000/#!/2/docker/dashboard
        server: local
        container: portainer
        description: Container management
        widget:
          type: portainer
          url: http://192.168.1.151:9000
          env: 2
          key: REDACTED

[colutti]

Can confirm that is not a problem only with portainer. It happens to all containers.

[hunkyn]

I am having the exact issue on all containers (Status offline)

  homepage:
    <<: *internalbase
    image: ghcr.io/benphelps/homepage:latest
    user: 1001:100 # Optional, change to your user and group IDs for permissions
    volumes:
      - /srv/dev-disk-by-label-downloads/mediatools/homepage:/app/config
      - /srv/dev-disk-by-label-downloads/mediatools/homepage/icons:/app/public/icons
      - /srv/dev-disk-by-label-downloads/mediatools/homepage/images:/app/public/images
      - /srv/dev-disk-by-label-Media:/hdd1
      - /srv/dev-disk-by-label-Media2:/hdd2
      - /var/run/docker.sock:/var/run/docker.sock # This passes your local docker socket to the container
    ports:
      - 3000:3000
    container_name: homepage

# For configuration options and examples, please see:
# https://github.com/benphelps/homepage/wiki/Docker-Integration

#my-docker:
#  host: 127.0.0.1
#  port: 2375

#other-docker:
#  socket: /var/run/docker.sock

local:
 socket: /var/run/docker.sock

- Utilities:
   - Media Portainer:
       icon: portainer.png
       href: http://192.168.1.151:9000/#!/2/docker/dashboard
       server: local
       container: portainer
       description: Container management
       widget:
         type: portainer
         url: http://192.168.1.151:9000
         env: 2
         key: REDACTED

Try passing the IP address for docker server and see if that helps?

[C8opmBM]

Can you be more specific? Where should I pass the IP?

Also I'm getting 500 error in browser and the log is printing

Failed to discover services, please check docker.yaml for errors

[C8opmBM]

Console output

Failed to load resource: the server responded with a status of 500 () /api/docker/status/portainer/local:1

[colutti]

I am investigating the issue, with no luck so far but I do see an improvement. This code should not catch the exception, or unless it should re-raised it so we can actually see what is going on. It is not a good practice to catch exception and do nothing about it:

[hunkyn]

Can you be more specific? Where should I pass the IP?

Also I'm getting 500 error in browser and the log is printing

Failed to discover services, please check docker.yaml for errors

In the services.yaml file, where you have server: local, instead try passing the url example server: 192.168.xx.x. I tried with an alias and it did not work for me but when I passed IP it worked so it might work for you as well.

[C8opmBM]

I've tried to pass the ip, same error. Thanks for the suggestion.

[benphelps]

I am investigating the issue, with no luck so far but I do see an improvement. This code should not catch the exception, or unless it should re-raised it so we can actually see what is going on. It is not a good practice to catch exception and do nothing about it:

The exception is being caught until I can properly handle formatting errors in the YAML files. As that's the primary issue and it's errors are non-helpful.

I'll pass the exception through, to help with debugging.

[benphelps]

So this all probably has to do with the user your container is running as.

You can try removing the user: 1000:1000 line from your docker compose and see if that fixes it.

[C8opmBM]

So this all probably has to do with the user your container is running as.

You can try removing the user: 1000:1000 line from your docker compose and see if that fixes it.

Perfect! This was the issue! Removing user from docker compose fixes it.
Also this fixes for me #168

[colutti]

it fixes mine too, althought I would like to know why since all my containers run using the same user as the host.

[huzzyz]

Thank you. That fixed it.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns.