Bug 509648

Summary: discover should take /etc/ostree/auth.json into account
Product: [Applications] Discover Reporter: slartibart70
Component: rpm-ostree BackendAssignee: Plasma Bugs List <plasma-bugs-null>
Status: CONFIRMED ---    
Severity: wishlist CC: aleixpol, kdedev, mariamfahmy66, nate, travier
Priority: NOR    
Version First Reported In: 6.4.80   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description slartibart70 2025-09-18 17:49:30 UTC 
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?
Comment 1 slartibart70 2025-09-18 17:52:42 UTC 
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)
Comment 2 TraceyC 2025-09-22 17:08:56 UTC 
Sending along for consideration