Preconfigure Container Registry in Codespaces #25613
-
I’m trying to preconfigure a private container registry in a CodeSpace so workshop participants can use it. According to the docs it’s all pretty straight forward, but it looks like I’m missing something, because it won’t work, and the docs aren’t clear on what I need to expect on the receiving end. What I’ve done so far:
If I read the docs correctly, this should make sure docker can pull from ghcr using my credentials, but all I get is an error:
I searched the vscode-container repository for a hint to something I may have to configure on my custom container, but I don’t really see anything wrong. Custom container dockerfile:
I tried in the standard vscode container and see the same behavior. I must be doing something wrong. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Of course it’s very simple once you see it! When you open the Secrets in your GitHub settings you end up on the ACTIONS Secrets page. And the fact that there are 3 other secrets pages is hidden because the expanded settings menu has scrolled off screen. So make sure you add these secrets to the CODESPACES Secrets page: Then rebuild the Codespace. |
Beta Was this translation helpful? Give feedback.
Of course it’s very simple once you see it!
When you open the Secrets in your GitHub settings you end up on the ACTIONS Secrets page. And the fact that there are 3 other secrets pages is hidden because the expanded settings menu has scrolled off screen.
So make sure you add these secrets to the CODESPACES Secrets page:
Then rebuild the Codespace.