https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
q
I wouldn't have created it, maybe if the repo doesn't exist, it needs to create it for me?
p
I think (not sure) I've seen cases where the package needed to exist first before things worked correctly, but it looked like it was already there anyway…
f
I think the package gets created automatically, but it will be private, and you have to explicitly mark it as public before anybody can pull it without authentication.
q
so, github seems to think things exist
How would I mark it as public, and wouldn't that be something the workflow should do?
f
It seems already public; I can pull it
q
f
I wonder how you made it public; whenever I create a repo via 
docker push
it is private
q
So that doesn't explain why the workflow failed
By default, if you publish a package that is linked to a repository, the package automatically inherits the access permissions (but not the visibility) of the linked repository. For example, a user who has read access to the linked repository will also have read access to the package. When a package automatically inherits access permissions, GitHub Actions workflows in the linked repository also automatically get access to the package.
I have no idea
and don't know that I know anyone who knows anything about this stuff 😞
I didn't do any of this, it was merely rancher desktop's workflows!
f
I don't even know what it means that a package is linked to a repo
We have a workflow that pushes images???
q
apparently?
f
Ah, ok, it is something Mark did for RDX
q
@proud-jewelry-46860?
f
Yes
q
ok, i'm going to give up on this problem for the day (probably = week). But I'll see slack messages eventually if people have insight/want me to try things.
p
Ah, I was poking around in my fork, and I see that there's a package setting for Actions permissions. Somewhere around https://github.com/users/jsoref/packages/container/rancher-desktop%2Frdx-host-api-test/settings probably (I edited my URL… it's (user profile) → Packages (tab on top) → 
rdx-host-api-test
→ Package settings (right margin) → Manage Actions access section. It's set to Role: Admin for me. I'm an idiot, you already have that…
Hmm, https://github.com/jsoref/rancher-desktop/actions/runs/5349256988/jobs/9700216994 appears to have succeeded, and I don't understand why…
2 Views
Open in Slack
PreviousNext
Powered by