Im getting the following output, noticed that the error doesnt occur when only one build is running, there seem to be a conflict when other builds are running aswell. I have 2 builder.
Using the existing docker config file.Removing blacklisted property: authsRemoving blacklisted property: credsStore$ docker login -u z*******t -p ******** https://docker.pkg.github.com
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
Error saving credentials: error storing credentials - err: exit status 1, out: The specified item already exists in the keychain.
Related
Update: I removed Docker entirely by following this link:
https://askubuntu.com/a/1021506
I then reinstalled Docker like this:
https://docs.docker.com/engine/install/ubuntu/
Right after the reinstall, mvn jib:dockerBuild worked without sudo.
When running gcloud auth configure-docker, this was added to .docker/config.json
"credHelpers": {
"asia.gcr.io": "gcloud",
"eu.gcr.io": "gcloud",
"gcr.io": "gcloud",
"marketplace.gcr.io": "gcloud",
"staging-k8s.gcr.io": "gcloud",
"us.gcr.io": "gcloud"
}
and problem reappears. Removing the above section manually in config.json made mvn jib:dockerBuild work again.
Running the following command
mvn jib:dockerBuild
with a plain Micronaut 3.0.2 project gives this output:
[ERROR] Failed to execute goal com.google.cloud.tools:jib-maven-plugin:2.7.1:dockerBuild (default-cli) on project barn-validation-step: Build to Docker daemon failed, perhaps you should make sure your credentials for 'registry-1.docker.io/library/openjdk' are set up correctly. See https://github.com/GoogleContainerTools/jib/blob/master/docs/faq.md#what-should-i-do-when-the-registry-responds-with-unauthorized for help: Unauthorized for registry-1.docker.io/library/openjdk: 401 Unauthorized
[ERROR] GET https://auth.docker.io/token?service=registry.docker.io&scope=repository:library/openjdk:pull
[ERROR] {"details":"incorrect username or password"}
When using the same command with sudo:
sudo env "PATH=$PATH" mvn jib:dockerBuild
build is successful. Build is also successful when using Maven step in Azure Pipelines.
I've read the content from the URL in the error message. I've also spent a couple of hours searching for solutions elsewhere, no luck so far.
I'm able to login using docker login, and
curl https://auth.docker.io/token?service=registry.docker.io&scope=repository:library/openjdk:pull
returns a token
If you provide wrong username or password, Docker Hub returns the following error message:
$ docker login -u foo -p bar
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
Error response from daemon: Get https://registry-1.docker.io/v2/: unauthorized: incorrect username or password
Note the same message you see when running Jib. The message is from Docker Hub:
[ERROR] {"details":"incorrect username or password"}
Also from the fact that sudo env "PATH=$PATH" mvn jib:dockerBuild worked, it must be that Jib running in your local user environment uses different username and password information.
Jib searches various locations to retrieve registry credentials (which is simply a username and password pair), so it must be that the credentials that Jib picks up when running as root and when running as your user are different. As explained in the doc, Jib log will reveal where it picked up credentials. For example,
Using credentials from Docker config (/home/user/.docker/config.json) for localhost:5000/java
or
Using credential helper docker-credential-gcr for gcr.io/project/repo
Check the log to identify where the credentials are coming from and fix them.
This command caused the trouble:
gcloud auth configure-docker`
By using
gcloud auth configure-docker eu.gcr.io
instead, everything works as depicted. The reason seems to be that with the latter command, there is no collision between Jib base image repository and my target repository (which is located inside eu.gcr.io).
I've managed to install influxdb2 and login to the web ui at localhost:8086 with the default username/pass admin/admin. But when I try to login now with the same credentials i get an error saying "Could not sign in" as shown here: Running systemctl status influxdb gives me this output: This persists after reboots and reinstalls of influxdb. Is there some way to hard reset the password or to disable the authentification?
You can reset your InfluxDB 2 administrator password by recovering a admin token if you have access to the installation filesystem.
Find influxd.bolt on the host or in the container: /var/lib/influxdb2/influxd.bolt
Search this mixed text and binary json file for strings like your known username or token.
cat /var/lib/influxdb2/influxd.bolt | strings | grep "admin's Token"
{"id":"1234567898000000",
"token":"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx==",
"status":"active",
"description":"admin's Token",
With an admin-privileged token, you can update the password with the Influx Command Line Interface (CLI) command influx user password. For example:
$ docker exec -it 85e4df16a429 influx user password -n admin -t xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx==
? Please type your new password *********************
? Please type your new password again *********************
Your password has been successfully updated.
$
It happened the same to me, I created a user and then I forgot the password.
For those who work in Windows, go to C:\Users\YourName and delete .influxdbv2.
I forgot i created a new user, organization and bucket when first running influxdb.
I've managed to solve it by purging all the influxdb files by running dpkg --purge influxdb2 and then reinstalling.
While not in any container, I try docker login quay.io.
When not as root I get: Remote error from secret service: org.freedesktop.Secret.Error.IsLocked: Cannot create an item in a locked collection
Error saving credentials: error storing credentials - err: exit status 1, out: Cannot create an item in a locked collection
When root (not running in an X11 session because I shouldn't have to?) I get: Error saving credentials: error storing credentials - err: exit status 1, out: Cannot autolaunch D-Bus without X11 $DISPLAY
Looking right now for an online "real howto" for setting up Docker in Ubuntu and installing something that's stored on Quay. (Quay's documents, such as they are, merely assume that you know what you're doing already.)
I just installed 19.03.2 on my windows 10 laptop. When I attempt any docker command such as docker login or docker version, I get the warning as below.
WARNING: Error loading config file: C:\Users\user-id.docker\config.json: json: cannot unmarshal string into Go value of type configfile.ConfigFile
My config.json looks as below
"quay.io": {"<hidden for security reasons>"}
Could not find any reference to error for docker login in google search. There are reference for type string, but not for configfile.
Any help is appreciated. Thanks in advance.
Clear the file, delete everything in: C:\Users\user-id.docker\config.json
From the command line run:
docker login -u your_docker_username "https://index.docker.io/v1/"
Type your password
Output:
Login Succeeded
It will generate "auths" credentials in C:\Users\user-id.docker\config.json file
You can use dokcer login again with no problems after that
I begin to use NVIDIA GPU CLOUD Deep Learning platform. I try to pull in the console (Command Prompt):
docker pull nvcr.io/nvidia/pytorch:17.10
and get the message:
Error response from daemon: Get https://nvcr.io/v2/: unauthorized: authentication required
What is my fault?
This error is an indication that the user is not authorized via login and API key. It is necessary to authorize in the console:
docker login nvcr.io
Username: $oauthtoken
Password: <Your Key>
You are not going to look for a special Username. $oauthtoken is the username.
docker login --username "$oauthtoken" --password "{REDACTED}" nvcr.io
I failed the above command, since it is pain to type password
When run 'docker login', you just input '$oauthtoken' as your name. Not the nickname of your nvidia.NGC.