charmcraft 1.4.0: impossible to login to charmhub
Metadata
Current evaluation
Closed as expected behavior. Charmcraft falls back to a non-persistent memory ring on headless systems lacking a keyring, preventing credential persistence. Maintainers advised exporting credentials via environment variables instead of implementing a code fix.
Suggested action: —
No scores available.
Issue body
```bash
$ charmcraft login
Opening an authorization web page in your browser.
If it does not open, please open this URL:
https://api.jujucharms.com/identity/login?did=870565472d077a4ab0c6a67e28ea4f205ffa441ccc3e037ffaa42d0dacf07fa7
Logged in as 'omnivector-solutions'.
$ charmcraft whoami
You are not logged in to Charmhub.
$ snap list | grep charmcraft
charmcraft 1.4.0 761 latest/stable canonical* classic
```
Am I missing something here?
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as expected behavior. Charmcraft falls back to a non-persistent memory ring on headless systems lacking a keyring, preventing credential persistence. Maintainers advised exporting credentials via environment variables instead of implementing a code fix. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed as intended behavior. Charmcraft requires a system keyring to persist credentials, which headless servers lack. Developers clarified this is not a bug and advised exporting credentials via environment variables. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as expected behavior. Charmcraft could not persist credentials without a system keyring on the headless server. Maintainers clarified that exporting tokens via environment variables is the required workaround. No code fix needed. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as expected behavior. Charmcraft fails to persist credentials on headless systems lacking a keyring. Maintainers provided an environment variable workaround and noted a fix for the silent fallback behavior is pending release. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #901 Charmcraft login on remote device has unhelpful error message | charmcraft | closed | Closed. The unhelpful remote login error is tracked upstream in craft-store issue #58, as the fix requires changes to the underlying authentication library rather than Charmcraft itself. | |
| #719 [1.5.0] Charmcraft login not finding keyring | charmcraft | closed | Closed without a code fix. Identified as an environmental configuration issue. Users resolved it by using dbus-run-session or explicitly setting PYTHON_KEYRING_BACKEND to bypass automatic keyring detection failures. | |
| #2336 Can't login in headless multipass VM with 24.04 | charmcraft | open | charmcraft login crashes in headless Multipass VMs (Ubuntu 24.04) because the keyring library falls back to the null keyring, so credentials can't be stored. Reporter self-diagnosed the gap in craft-store auth.py and shared a PYTHON_KEYRING_BACKEND workaround; no maintainer has responded. | |
| #668 `charmcraft status` should work without needing to log in | charmcraft | closed | Closed as rejected. Maintainer confirmed all Charmhub operations require authentication, making the requested unauthenticated status check impossible to implement within charmcraft. |