Recommend a workflow for using gh inside of a development docker container

[ggoretkin-bdai]

One approach to using the gh CLI from inside a development docker container was to mount the ~/.config/gh/hosts.yml file, as explained in https://dev.to/r7kamura/github-cli-on-devcontainer-3od7 . However, now the secrets are stored in e.g. the GNOME keyring.

What is the recommended way to use gh from within a development docker container?

[samcoe]

@ggoretkin-bdai Thanks for writing in. I converted the issue into a discussion as it did not correspond to a bug or features request.

Unfortunately, I do not have an answer for you as no one on our team uses docker for local development. Assuming you are using a Linux image you could investigate how to setup dbus to run inside the container and communicate with the host system as that is what gh uses to securely store auth tokens.

[cedric-spinergie]

Hi @samcoe and thanks for this reply. I just upgraded our gh cli in our dev setup and this new auth broke the credentials. Is there a way to force it to revert to the file storage instead of the keyring or should I downgrade and freeze my gh version?
Thanks in advance for answering.

[samcoe]

@cedric-spinergie You can use the --insecure-storage flag when doing gh auth login to go back to how we previously stored credentials.

[JoinEvgen]

Dats great to hear tell me more about it

Получите

[johnhkchen]

For people who are using devcontainers (VS code's variant), there is a feature you can request from within devcontainer.json

"features": {
    "ghcr.io/devcontainers/features/github-cli:1": {}
}

https://github.com/devcontainers/features/tree/main/src/github-cli

[giallu]

I would also like to find a solution for this.
I replaced the container in my vscode devcontainer setup with a RHEL8 one by providing my own base image and now I can't find a simple way to access GH releases from within the container