Do we really need user/token for LSCR support?

[armond-avanes]

I'm running WatchTower beside WUD in my home lab. I've noticed that WatchTower works pretty fine with LSCR registry with no user/token set for it. But for WUD, I need to setup user/token which I've not done it yet. How does WatchTower do it if LSCR really forces user/token usage?

UPDATE: Another example is Diun (Docker Image Update Notifier - https://crazymax.dev/diun/) which doesn't have any specific config for LSCR. I'm not a Diun user but looks like it's working fine with that registry.

[rufo]

I only just set up WUD and popped into the discussions to see if another question I had was answered, so I don't know if I'm missing something more here - but to get the LinuxServer.io registry recognized, all I added was WUD_REGISTRY_CUSTOM_LINUXSERVER_URL=https://lscr.io as an environment variable and WUD seemed to pick it up fine for me. (You can change LINUXSERVER to whatever you want and the registry will be named that in the UI - I mention it as I haven't fully decided if I wanted LINUXSERVER or LSCR yet 😛)

[armond-avanes]

I hadn't thought to do it in a custom way. Thanks for the idea. I'll give it a try.

But my main question is till in place... why does the built-in LSCR integration require to setup user/token while the entire LSCR registry is open and doesn't need any kind of authentication and other softwares are interacting with it without any authentication?

[armond-avanes]

Just noticed the following authentication error when using custom LSCR:

Error when processing (401 - {"errors":[{"code":"UNAUTHORIZED","message":"authentication required"}]})

So looks like the custom solution doesn't work and the built-in one with user/token should be used instead.