I'm using my own bootc-based atomic desktop (similar to kinoite but with more tools for corporate usage) For updates, i use sudo bootc switch [container-registry/path] with an access token provided in /etc/ostree/auth.json When i start plasma-discover (as user) i see in the logs that skopeo is not succesful in contacting my container-registry (error 403 unauthorized) My workaround is to do a skopeo/podman login to my registry first, then plasma-discover is happy as well For my use-case, i do want a generally provided access-token in a central place (etc/ostree/auth.json) so that a user does not need to login to anything first when doing updates What do you think of this enhancement, that plasma-discover is extending its strategy and will also look in /etc/ostree/auth.json if it doesn't find anything appropriate in run/user/1234/containers/auth.json? I know that skopeo is user-scoped, so this feature is better not provided by skopeo itself. But discover could (if skopeo returns errors) try to look somewhere else?
Operating System: Fedora Linux 42 KDE Plasma Version: 6.4.80 KDE Frameworks Version: 6.19.0 Qt Version: 6.9.2 Kernel Version: 6.16.7-200.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz Memory: 32 GiB of RAM (31.1 GiB usable)
Sending along for consideration