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

keychain or other secret store access when run in docker? #347

Open
ira-bv opened this issue Apr 3, 2022 · 1 comment
Open

keychain or other secret store access when run in docker? #347

ira-bv opened this issue Apr 3, 2022 · 1 comment

Comments

@ira-bv
Copy link

ira-bv commented Apr 3, 2022

Expected Behavior

when run in a docker container, gimme-aws-creds keeps asking for the okta password. naturally it has no access to the keychain store of the host OS (MacOS in my case), but Docker Desktop has a secrets store built into it. Is this an interface that needs to be written or a missing setup stage?

Possible Solution

add support for the Docker Secrets Management and setup steps.

Steps to Reproduce (for bugs)

  1. set up native gimme
  2. login and store pass in keychain
  3. setup gimme in docker
  4. note running gimme asks for the password again on ever run, offers no store option

Your Environment

  • App Version used: 2.4.4
  • Environment name and version: MacOS (via Brew) vs dockerfile (built from latest source)
  • Operating System and version: MacOS 12.3.1, Docker engine v20.10.8
@robomfeinberg
Copy link

I solved this problem by using keyrings.alt. Just be careful not to build/push a public container with your keyring. You can also use docker/docker-credential-helpers which I am told works well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants