rancher: Pipeline / Build / Error authenticating: exit status 1

What kind of request is this (question/bug/enhancement/feature request):

question or possible bug

Steps to reproduce (least amount of steps as possible): Install a fresh cluster, with RKE Install a fresh Rancher 2.1.1 ( 2.1.0 have the same problem )

Result:

If I add a private repository ( docker-registry from Catalog or from Helm-incubator ), or even if I try to use the DockerHub private repository, each time the Pipeline fail on the build part, about an « Error authenticating »:

11:05:34 [pipeline_p-bvz7d-5] Running shell script 11:05:36 + /usr/local/bin/dockerd-entrypoint.sh /bin/drone-docker 11:05:36 + /usr/local/bin/dockerd -g /var/lib/docker 11:05:55 EXITCODE 0time=“2018-10-21T11:05:52Z” level=fatal msg=“Error authenticating: exit status 1”

Other details that may be helpful: I never used Rancher before, so may be I’ve missed something. But after 3 days of multiples tests, and search in the issues, I’ve found there is multiple bugs around private registry. One bug have been fixed in 2.1.1, so I’ve tried to remove everything (reformat all my cluster disks) and re-install the 2.1.1, but I get the same issue. I’ve found a ticket about registry that should be fixed in 2.1.2, I’m not known if it’s really related.
Is it a bug, do I need to wait the version 2.1.2 ?

Environment information

Rancher version: 2.1.1
Installation option (single install/HA): single on a HA cluster v1.12 installed with RKE

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Custom, Imported
Machine type (cloud/VM/metal) and specifications (CPU/memory): metal, 11 nodes 32Go RAM / 8vCPU
Kubernetes version (use kubectl version): 1.12.0

Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"clean", BuildDate:"2018-10-05T16:46:06Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.0", GitCommit:"0ed33881dc4355495f623c6f22e7dd0b7632b7c0", GitTreeState:"clean", BuildDate:"2018-09-27T16:55:41Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}

Docker (use docker info):

Containers: 28
 Running: 18
 Paused: 0
 Stopped: 10
Images: 12
Server Version: 18.06.1-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e
runc version: 69663f0bd4b60df09991c08812a60108003fa340
init version: fec3683
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.15.0-34-generic
Operating System: Ubuntu 18.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 15.3GiB
Name: cp1.readact.page
ID: RJJU:SN4M:6G2H:HL2D:UL6S:UF5Y:WOFD:YJEL:TBT5:RYEF:U7DV:5IZI
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): 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

( installed from get.docker.com, channel stable, 18.06.x seems to be the new references for k8s on v1.12.x )

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 22 (5 by maintainers)

Most upvoted comments

If you use the auto-generated docker registry,

remove pushRemote & registry field for publish step
add imagePullSecrets with pipeline-docker-registry secret name in deployment

gitlawr on Oct 29, 2018

@lakano Basically when the docker login fails you will see this error. We’ve found users hitting the same error message due to different causes, like dns issue/improper configs of registry. To diagnose you can enable debug mode of dockerd to get more information, e.g.:

stages:
- name: build
  steps:
  - publishImageConfig:
      dockerfilePath: ./Dockerfile
      buildContext: .
      tag: myproject
      pushRemote: true
      registry: index.docker.io
    env:
      PLUGIN_DEBUG: "true"

gitlawr on Oct 24, 2018

@iwin4aids You can give additional envvars to tweak the build image step:

stages:
- name: build
  steps:
  - publishImageConfig:
      dockerfilePath: ./Dockerfile
      buildContext: .
      tag: myproject
      pushRemote: true
      registry: index.docker.io
    env:
      PLUGIN_DEBUG: "true"
      PLUGIN_INSECURE: "true"

You can check more in the docs(clicking on By Yaml tab of Build and Publish Images) https://rancher.com/docs/rancher/v2.x/en/tools/pipelines/configurations/#build-publish-image

gitlawr on Oct 25, 2018