I'm getting "API Error" when running with docker swarm and the container runs in a different server

[tristangrimaux]

Description

Everything is running smoothly with homepage, the services are added automatically in the corresponding groups but it displays "API ERROR" on containers that are running on a different docker node than homepage

homepage version

v0.8.12 (12ec1cf, Apr 17, 2024)

Installation method

Docker

Configuration

in the docker.yaml it reads

mainswarm:
  socket: /var/run/docker.sock
  swarm: true

or with dockerproxy

mainswarm:
  swarm: true
  host: 10.10.20.8
  port: 2375

Container Logs

No response

Browser Logs

No response

Troubleshooting

house_homepage.1.j32m5x892p2o@mariner    | [2024-05-03T23:58:48.402Z] error: <dockerStatusService> TypeError: Cannot read properties of null (reading 'conn')
house_homepage.1.j32m5x892p2o@mariner    |     at handler (/app/.next/server/pages/api/docker/status/[...service].js:89:86)
house_homepage.1.j32m5x892p2o@mariner    |     at Object.apiResolver (/app/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/server/api-utils/node.js:366:15)
house_homepage.1.j32m5x892p2o@mariner    |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
house_homepage.1.j32m5x892p2o@mariner    |     at async NextNodeServer.runApi (/app/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/server/next-server.js:481:9)
house_homepage.1.j32m5x892p2o@mariner    |     at async Object.fn (/app/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/server/next-server.js:741:37)
house_homepage.1.j32m5x892p2o@mariner    |     at async Router.execute (/app/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/server/router.js:252:36)
house_homepage.1.j32m5x892p2o@mariner    |     at async NextNodeServer.run (/app/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/server/base-server.js:365:29)
house_homepage.1.j32m5x892p2o@mariner    |     at async NextNodeServer.handleRequest (/app/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/server/base-server.js:303:20)
house_homepage.1.j32m5x892p2o@mariner    |     at async Server.<anonymous> (/app/server.js:19:5)
house_homepage.1.j32m5x892p2o@mariner    | [2024-05-03T23:58:48.403Z] error: <dockerStatsService> TypeError: Cannot read properties of null (reading 'conn')
house_homepage.1.j32m5x892p2o@mariner    |     at handler (/app/.next/server/pages/api/docker/stats/[...service].js:89:86)
house_homepage.1.j32m5x892p2o@mariner    |     at Object.apiResolver (/app/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/server/api-utils/node.js:366:15)
house_homepage.1.j32m5x892p2o@mariner    |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
house_homepage.1.j32m5x892p2o@mariner    |     at async NextNodeServer.runApi (/app/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/server/next-server.js:481:9)
house_homepage.1.j32m5x892p2o@mariner    |     at async Object.fn (/app/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/server/next-server.js:741:37)
house_homepage.1.j32m5x892p2o@mariner    |     at async Router.execute (/app/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/server/router.js:252:36)
house_homepage.1.j32m5x892p2o@mariner    |     at async NextNodeServer.run (/app/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/server/base-server.js:365:29)
house_homepage.1.j32m5x892p2o@mariner    |     at async NextNodeServer.handleRequest (/app/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/server/base-server.js:303:20)
house_homepage.1.j32m5x892p2o@mariner    |     at async Server.<anonymous> (/app/server.js:19:5)

[glime-ai[bot]]

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

---

Based on the provided context and the error logs, it seems that the issue is related to the Docker configuration, specifically with the Docker status and stats services. The error messages indicate that there is a problem with reading properties of null, which suggests that there might be an issue with the connection to the Docker API or the way the Docker status is being retrieved.

Given that the error occurs with containers running on a different Docker node than Homepage, it's possible that the connection to the Docker API on the remote node is not correctly established or that there are network issues preventing proper communication.

Here are some steps you can take to troubleshoot the issue:

1. Verify that the Docker API is accessible from the Homepage container. If you are using a Docker socket proxy, ensure that it is correctly configured and that the Homepage container can communicate with it.

2. Check the network configuration to ensure that the Homepage container can reach the remote Docker node. This might involve checking firewall rules, network policies, or container network configurations.

3. Review the docker.yaml configuration file to ensure that the settings for the remote Docker node are correct. Pay special attention to the host and port settings if you are using a Docker socket proxy.

4. If you are using Docker Swarm, ensure that the swarm attribute is set to true in the docker.yaml configuration, as you have done in your configuration.

5. Check the Homepage logs for more detailed error messages that might provide additional clues about the issue.

6. Since the error message mentions a problem with the 'conn' property, it might be helpful to look into the Homepage source code, specifically at the files mentioned in the error logs ([...service].js), to understand how the Docker status and stats services are implemented and where the 'conn' property is expected to be defined.

7. If you are unable to resolve the issue, consider reaching out to the Homepage community for support. You can use the 'Ask AI' button in the Homepage docs, open a GitHub discussion, or join the #ai-support channel on Discord for assistance.

Remember to check the official Homepage documentation and GitHub repository for any updates or additional troubleshooting tips that might be relevant to your issue.

This comment was generated by Glime.

[Pinkbyte]

I am having the same problem

[DeepSkyWonder]

I am experiencing the same error also. Docker service discovery works in a swarm (awesome), but docker service stats only work for the node on which Homepage is deployed and display an API error for services deployed on other nodes.

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.