Open Time0o opened 4 months ago
It seems to me what you've described should work.
I'm unfamiliar with using pip with keyring. Can you link to where this support is described?
My first guess is that the username/password being saved isn't matching exactly for what pip is querying. Have you confirmed you are able to retrieve the stored password? Do you have any way to confirm that pip is requesting the password for that exact system/user? Are you sure that keyring is configured in the environment where pip can use it?
Describe the bug
I have the following situation: In a GitLab CI job, running inside a
debian:latest
Docker container, I want to install a package from a GitLab package registry using the simplest possiblekeyring
setup. This is to assert that the installation instructions I provide to users in the README actually do what they are supposed to do, I don't care if the backend used is actually secure.Here is my job definition:
This fails silently because
pip install
will still prompt for username/password. This does not happen on my local Ubuntu machine which uses the properSecretService
backend.keyring
's README contains instructions for using this backend in a privileged Ubuntu container. But my container runs Debian and is not privileged so I hoped I could just use a "dummy" backend. Why can't I?To Reproduce
docker run -it debian:latest
keyring
andkeyring.alt
in a virtual env.import
provider.pip install
.Expected behavior
pip install
will use the credentials provided tokeyring
, even when using the plaintext backend.Environment
debian:latest
container.