

So the docker container image-watcher and update-coordinator seems quite incongruous with the rest of the tool. It looks like a “network visibility tool” with the container manager just tacked on as scope creep.
I presume if the container is actioning the updates for you, it also requires docker socket privileges? I imagine that will give a number of people pause about installing it on their homelabs, as “cool looking vibe-coded personal project with docker socket privileges” is a ticking time bomb from a cybersecurity perspective.
If it does require docker socket (and Can’t imagine how the container management would work if it doesn’t) you night have more success getting uptake in users for feedback on the main features if you remove the tacked on container manager and just keep that part for your own personal implementation of the application.
this is the only one you need to know, tbh. its an amalgamation of mirrors of basically every other public archive