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.

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

[Bug] When WATCHATSTART is FALSE, no containers are listed in the UI #570

Closed
armond-avanes opened this issue Jan 19, 2025 · 3 comments
Closed
Assignees
Labels
enhancement New feature or request

Comments

@armond-avanes
Copy link

armond-avanes commented Jan 19, 2025

When I run the WUD container with WATCHATSTART=False and launch the web UI, I don't see any containers listed there.

I've not tested it further but most probably the containers are fetched/refreshed when WUD is going to check for the new versions. This makes sense from a WATCHER perspective, but from GUI point of view, the containers should be fetched at startup (or at least when the GUI is launched for the first time and there are no containers info yet) and shown there even if there are no watchers scheduled at WUD startup.

@fmartinou
Copy link
Collaborator

Hi,

Container discovery and update checking are executed at the same time.

I'm thinking about removing the WATCHATSTART option and forcing a watch at start only if the store is empty.

It will probably be more simple/usable 🤔

@fmartinou fmartinou added the enhancement New feature or request label Jan 21, 2025
@fmartinou fmartinou self-assigned this Jan 21, 2025
@fmartinou
Copy link
Collaborator

29cc983

@Fayyaadh
Copy link

So what do we do exactly when we don't want containers to be updated on startup of wud? Only at the intervals defined by the CRON?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants