Description
We have a software which will call docker xxx in its code.
a) It's ok in the past
b) After upgrade docker to 20.10.1, it reports next:
WARNING: Error loading config file: .dockercfg: $HOME is not defined
NOTE: we don't have HOME set in our env. I wonder if it's a bug? What's the root cause?
Should I add export HOME=/root in our software to act as a workaround, or you will fix it in future release?
Steps to reproduce the issue:
- Install 20.10.1
- unset HOME
docker ps or any other docker command will show warning.
Describe the results you received:
# docker ps
WARNING: Error loading config file: .dockercfg: $HOME is not defined
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
Describe the results you expected:
No warning.
Output of docker version:
Client: Docker Engine - Community
Version: 20.10.1
API version: 1.41
Go version: go1.13.15
Git commit: 831ebea
Built: Tue Dec 15 04:34:48 2020
OS/Arch: linux/amd64
Context: default
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 20.10.1
API version: 1.41 (minimum version 1.12)
Go version: go1.13.15
Git commit: f001486
Built: Tue Dec 15 04:32:45 2020
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.4.3
GitCommit: 269548fa27e0089a8b8278fc4fc781d7f65a939b
runc:
Version: 1.0.0-rc92
GitCommit: ff819c7e9184c13b7c2607fe6c30ae19403a7aff
docker-init:
Version: 0.19.0
GitCommit: de40ad0
Output of docker info:
Client:
Context: default
Debug Mode: false
Plugins:
app: Docker App (Docker Inc., v0.9.1-beta3)
buildx: Build with BuildKit (Docker Inc., v0.5.0-docker)
Server:
Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 3
Server Version: 20.10.1
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 269548fa27e0089a8b8278fc4fc781d7f65a939b
runc version: ff819c7e9184c13b7c2607fe6c30ae19403a7aff
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.19.0-13-amd64
Operating System: Debian GNU/Linux 10 (buster)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.593GiB
Name: shlava
ID: TULV:U34A:NIJQ:Y3SP:FKLM:UX64:YXUE:KMOU:LND5:HBBN:F5YV:F3D4
Docker Root Dir: /var/lib/docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
WARNING: No swap limit support
Description
We have a software which will call
docker xxxin its code.a) It's ok in the past
b) After upgrade docker to
20.10.1, it reports next:NOTE: we don't have HOME set in our env. I wonder if it's a bug? What's the root cause?
Should I add
export HOME=/rootin our software to act as a workaround, or you will fix it in future release?Steps to reproduce the issue:
docker psor any other docker command will show warning.Describe the results you received:
Describe the results you expected:
No warning.
Output of
docker version:Output of
docker info: