Use of instances (InstanceName)

[dimitricappelle]

Description

I have a question about the behavior I notice with instances.

On my compose file I have the following for a container

labels:
      - homepage.instance.internal-admin.group=$WALLOS_HOMEPAGE_GROUP
      - homepage.instance.internal-admin.name=Wallos
      - homepage.instance.internal-admin.description=$WALLOS_HOMEPAGE_DESCRIPTION (:$WALLOS_PORT)
      - homepage.instance.internal-admin.icon=tube-archivist.png
      - homepage.instance.internal-admin.href=$WALLOS_URL:$WALLOS_PORT
      - homepage.instance.internal-admin.ping=$WALLOS_URL:$WALLOS_PORT
      - homepage.instance.internal-admin.weight=$WALLOS_HOMEPAGE_WEIGHT

I have 2 homepage instances running with the following difference in my compose file:

HOMEPAGE_VAR_INSTANCE_NAME=internal-admin
HOMEPAGE_VAR_INSTANCE_NAME=internal-user

settings.yaml

instanceName: {{HOMEPAGE_VAR_INSTANCE_NAME}}

When I visit the the 'internal-user' page that has no labels for the particular container I see the service widget popup and disappear immediately. In the console on the browser I see the following: Failed to load resource: the server responded with a status of 400 (Bad Request)

Content of the response:

{
    "error": "Unable to find service, see log for details."
}

I'm wondering if this is normal behavior that it is briefly visible + the error? I would think the container is not "discovered" in my 'internal-user' homepage.

homepage version

v0.9.2 (af16956, Jun 6, 2024)

Installation method

Docker

Configuration

No response

Container Logs

No response

Browser Logs

No response

Troubleshooting

I tested the behavior in Firefox, Chrome and Safari with cleaning of all history, cache, ...
Behavior is always the same

[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 information provided, it seems that you are encountering an issue where a service widget briefly appears and then disappears with an error on the 'internal-user' instance of your Homepage setup. This behavior is likely not intended and could be due to a misconfiguration or a bug in the service discovery mechanism.

The service labels you've defined are specific to the 'internal-admin' instance, as indicated by the prefix homepage.instance.internal-admin. Therefore, the 'internal-user' instance should not be attempting to load this service at all since it does not have corresponding labels for that instance.

Here are a few steps you can take to troubleshoot this issue:

1. Ensure that the instanceName is correctly set in the settings.yaml for each instance and that there are no typos or mismatches between the instance names in the docker-compose file and the settings.yaml.

2. Verify that the service discovery mechanism is correctly filtering services based on the instance name. It should only discover services that have labels matching the current instance name.

3. Check the Homepage logs for any additional error messages or clues as to why the service is being incorrectly discovered or attempted to be loaded by the 'internal-user' instance.

4. Review the documentation for any updates or changes in the service discovery behavior that might affect how instances are handled in the version you are using (v0.9.2).

5. If the issue persists, consider filing a bug report with the Homepage repository, providing all the relevant configuration details and logs to help the developers diagnose and address the issue.

It's not normal for the service to be briefly visible and then disappear with an error. The expected behavior would be for the service not to appear at all on the 'internal-user' instance if it doesn't have the corresponding labels.

If you need further assistance, please provide additional details about your configuration, especially the parts of the docker-compose file related to the Homepage service definitions for both instances.

This comment was generated by Glime.

[dimitricappelle]

How does't one check point 2? There is nothing in the logs about all the discovered services (log is on debug).
It's only full of [2024-06-21T10:57:04.757Z] error: <service-helpers> Error constructing service using homepage labels for container 'wallos'. Ensure required labels are present. Which is not useful as I have not labels set because I don't want the service be discovered in that homepage instance.

[dimitricappelle]

It seems to work I don't use HOMEPAGE_VAR_INSTANCE_NAME in my settings.yaml but hardcode the value: instanceName: internal-user. Which is strange since the other HOMEPAGE_VAR_XXX work.

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