[Bug] Broken docker integration

[the-bukkit]

Description

Currently all container indicators are displaying "unkown" and when clicking on it and on "API Error Information" it just shows API Error: Unknown error

Steps to reproduce

1. Add service with container info in services.yaml
2. Open homepage

homepage version

v0.5.5 (d16fd0c)

Installation method

Docker

Configuration

Relevant snippet from service.yml:

- Jellyfin:
    icon: jellyfin
    href: http://jellyfin.intra.net
    description: Media Server
    server: local
    container: jellyfin

Container Logs

[2022-12-17T20:07:10.329Z] error: (node:1) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)

Browser Logs

Console output:

Other

Docker integration works fine on v0.5.0

I can ping the services and I can successfully check the api as described in troubleshooting

[GertJanH]

i had the same with 1 service, the config is now case sensitive

so maybe check the server and container names

[the-bukkit]

i had the same with 1 service, the config is now case sensitive

so maybe check the server and container names

I've just checked, the container name is spelled exactly the same as in the service.yaml

[shamoon]

You said it works on 0.5.0, how about 0.5.4? There were some changes to docker integration in .5 that weren’t meant to affect this but may have

also please post your docker config

[ashapiro-fn]

I'm having the same issue. Let me know what I can post to help diagnose. There was a docker update that came out for Debian bullseye in the last day or two, wondering if that could be contributing.

[shamoon]

As I mentioned above, it would be helpful to know if downgrading to 0.5.4 helps and to see people’s docker configuration file.

since I’m not seeing this and it doesn’t seem to be everyone I’m trying to figure out what the common thread is

[consenti]

I can confirm that a downgrade to 0.5.4 works.

My docker compose looks like this:

version: "3.8"
services:
homepage:
image: ghcr.io/benphelps/homepage:latest
container_name: homepage
environment:
- TZ=Europe/London
volumes:
- /volume1/docker/homepage:/app/config
- /volume1/docker/homepage/images:/app/public/images
- /var/run/docker.sock:/var/run/docker.sock
ports:
- 3000:3000
network_mode: mybridge
restart: unless-stopped

[shamoon]

Ok thanks. Sorry not your compose your docker.yaml config (and an example service)

[shamoon]

Presumably it’s related to #660 i need to look at it closely later. Hopefully can track it down quickly

[ashapiro-fn]

Just as a data point, the container status works for me for the remote docker endpoint, but not the local one, configs (partial) below.

docker.yaml

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

pi-docker:
host: 192.168.15.16
port: 2375

services.yaml (partial)
- Ombi:
icon: ombi.png
href: EXTERNAL ADDRESS
server: my-server
container: ombi
widget:
type: ombi
url: http://ombi:3579
key: KEY
- Sonarr:
icon: sonarr.png
href: EXTERNAL ADDRESS
server: my-server
container: sonarr
widget:
type: sonarr
url: http://sonarr:8989
key: KEY
- Sabnzbnd:
icon: sabnzbd.png
href: EXTERNAL ADDRESS
server: my-server
container: sabnzbd
widget:
type: sabnzbd
url: http://sabnzbd:8080
key: KEY

[consenti]

Ok thanks. Sorry not your compose your docker.yaml config (and an example service)

docker.yaml only has the following two lines active -
my-docker:
socket: /var/run/docker.sock

example service =
- Dozzle:
icon: dozzle.png
href: http://myserver.local:8892/
description: Docker Container Logs
server: 192.168.1.23 # The docker server that was configured
container: dozzle # The name of the container you'd like to connect

[shamoon]

I think there are some config errors here. server should be the name in your config

In both cases actually, should be my-docker

[ashapiro-fn]

Yeah, that fixed it actually. Weird, it was working fine with he config right up to the 0.5.5 update.

[shamoon]

I think defaults were being used previously and that’s what changed. In fact you guys had things misconfigured but it was falling back in a way to prevent the issue. LMK

[ashapiro-fn]

Yup, works now after fixing the config. Thank you for the help!

[consenti]

Works! THANKS

[shamoon]

OP please re-open if that’s not your issue

[the-bukkit]

Yup, had it misconfigured and got lucky before.

Thanks for helping!

[p6002]

What I need to use in "server" because it not works with any of my containers.

    href: http://192.168.1.163:9000
    description: droppy
    server: http://192.168.1.163:9000
    container: droppy

[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.