Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

docker login error saving credentials: error storing credential The name org.freedesktop.secrets was not provided by any .service files

未关闭
#7,148 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
冷清
技术栈
docker, go

调研方向

从 Ubuntu 22.04 的 WSL2 环境中报告的 docker logout/login 序列开始,重点关注凭据存储和 ~/.docker/config.json。将失败的 credential-helper 路径与文档中记录的 workaround 进行比较,并验证 docker login 能够成功存储凭据,且不会出现 org.freedesktop.secrets 错误。

由索引模型根据 Issue 内容生成。

描述

area/authentication kind/question status/0-triage version/29.7
Description

Cannot login to the container registry :

id12345@ubuntu2204 ~ $ docker login docker.artifactory.mycompany.com
Username: id12345
Password:
error saving credentials: error storing credentials - err: exit status 1, out: `The name org.freedesktop.secrets was not provided by any .service files`
Reproduce
  1. logout ( docker logout docker.artifactory.mycompany.com)
  2. login ( docker login docker.artifactory.mycompany.com)
Expected behavior
  1. authentication succeeds
  2. the credentials are stored into ~/.docker/config.json
docker version
Client: Docker Engine - Community
 Version:           29.7.1
 API version:       1.55
 Go version:        go1.26.5
 Git commit:        e9452d6
 Built:             Fri Jul 31 17:07:31 2026
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          29.7.1
  API version:      1.55 (minimum version 1.40)
  Go version:       go1.26.5
  Git commit:       c5b8ce9
  Built:            Fri Jul 31 17:07:31 2026
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v2.2.6
  GitCommit:        11ce9d5f3c68c941867e82890e93e815c1304f1b
 runc:
  Version:          1.3.6
  GitCommit:        v1.3.6-0-g491b69ba
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
docker info
Client: Docker Engine - Community
 Version:    29.7.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.36.0
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v5.3.1
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 10
  Running: 10
  Paused: 0
  Stopped: 0
 Images: 12
 Server Version: 29.7.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 CDI spec directories:
  /etc/cdi
  /run/cdi
 Discovered Devices:
  cdi: nvidia.com/gpu=all
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 11ce9d5f3c68c941867e82890e93e815c1304f1b
 runc version: v1.3.6-0-g491b69ba
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.18.33.2-microsoft-standard-WSL2
 Operating System: Ubuntu 22.04.5 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 9.713GiB
 Name: ubuntu2204
 ID: 84dff749-cac8-4593-9f58-d7deffd81138
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
  ::1/128
 Live Restore Enabled: false
 Firewall Backend: iptables
  EnableUserlandProxy: true
  UserlandProxyPath: /usr/bin/docker-proxy
Additional Info

Workaround consists in adding credentials manually (not plain text but BASE64 encoded) :

echo -n 'id12345:YOUR_PASSWORD' | base64 -w0

and

cat > ~/.docker/config.json <<EOF
{
  "auths": {
    "docker.artifactory.mycompany.com": {
      "auth": "BASE64_VALUE"
    },
    "docker-public.artifactory.mycompany.com": {
      "auth": "BASE64_VALUE"
    }
  }
}
EOF
主要语言
Go
星标
6.1k
派生
2.2k
平均合并
2 天 2 小时
30 天内合并 PR
28

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

docker/cli 的其他 Issue

查看 docker/cli 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。