Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] An OS keyring couldn't be identified #4

Closed
1 task done
825i opened this issue Jul 12, 2023 · 4 comments
Closed
1 task done

[BUG] An OS keyring couldn't be identified #4

825i opened this issue Jul 12, 2023 · 4 comments

Comments

@825i
Copy link

825i commented Jul 12, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Trying to sign in with Github asks me to create a classic auth token. I make the token but when trying to paste it into VSCodium when it asks. I get the error shown below:

Screenshot 2023-07-13 011554

Expected Behavior

I should be able to paste the auth token and have it save. Instead, every time I want to do a sync with Github I have to sign in again via browser. Because "gnome-keyring" is already found on the system, shouldn't it be set up to be used?

The docs stated the container should be run with:

code --password-store="gnome"

But this didn't fix the issue.

Steps To Reproduce

  1. Make a git repo
  2. Push the repo
  3. Asked to sign in to Github
  4. Asked to set a classic auth token
  5. Make one
  6. Paste it into VSCodium
  7. Given the above error
  8. Must sign into Github every time you make a commit

Environment

- OS: Unraid
- How docker service was installed: via Unraid

CPU architecture

x86-64

Docker creation

docker run
  -d
  --name='vscodium'
  --net='bridge'
  -e TZ="Europe/Frankfurt"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="vscodium"
  -e 'PUID'='100'
  -e 'PGID'='1000'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:3000]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/vscodium-icon.png'
  -p '3000:3000/tcp'
  -p '3001:3001/tcp'
  -v '/mnt/user/appdata/vscodium':'/config':'rw'
  --cap-add=IPC_LOCK
  --shm-size=1gb 'lscr.io/linuxserver/vscodium'
fede1756d9bf212768daaf8da34f41bb6411792bada28202346345fc4df43459

The command finished successfully!

Container logs

[migrations] started
[migrations] no migrations found
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗ 
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝ 

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────

[custom-init] No custom files found, skipping...
[ls.io-init] done.
Obt-Message: Xinerama extension is not present on the server
 2023-07-13 01:17:47,549 [PRIO] Connections: accepted: @192.168.1.77_1689200267.543434::websocket
@github-actions
Copy link

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@825i
Copy link
Author

825i commented Jul 12, 2023

I just tried adding "password-store": "gnome" to \\TOWER\appdata\vscodium\.vscode-oss\argv.json as instructed by Microsoft, but that didn't work either after restarting the container. So I'm out of ideas.

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

@LinuxServer-CI LinuxServer-CI closed this as not planned Won't fix, can't repro, duplicate, stale Oct 12, 2023
Copy link

This issue is locked due to inactivity

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Archived in project
Development

No branches or pull requests

2 participants