Piplenes: docker login can not perform an interactive login from a non TTY

[Sergey Dolin]

I am trying to push the build docker image from within pipeline to docker hub and get and error:

==
+ docker login -u $DOCKER_USERNAME -p $DOCKER_PASSWORD
Error: Cannot perform an interactive login from a non TTY device
==

The full yml is:
==
pipelines:
branches:
master:
- step:
script:
- echo "$DOCKER_USER_NAME $DOCKER_PASSWORD"
- docker build -t s4ysolutions/spartan-resume-server -f docker/server.Dockerfile .
- docker login -u $DOCKER_USERNAME -p $DOCKER_PASSWORD
- docker push s4ysolutions/spartan-resume-server
# - docker build -t s4ysolutions/spartan-resume-front -f docker/front.Dockerfile .
#- docker push s4ysolutions/spartan-resume-front
options:
docker: true

[TPaz · Accepted solution]

I had exactly the same issue.

then I realized that in another repo it worked. So then I realized each Repo needs to have it's own environment variables set up. If you don't set up the DOCKER_USERNAME and DOCKER_PASSWORD in your example under the "Environment variables" section in the Repository settings, it would raise that confusing docker terminal (tty) error.

Can find the settings probably in this URI: <your_repo_name>/admin/addon/admin/pipelines/repository-variables

Once I fixed that, it worked fine.

I guess you already figured that out :) but for others to come...

[chirag_gajjar]

How can we find where to configure the Docker_username and docker_password.

[Optimum-Web]

HI all,  I have exactly the same problem with login. I set DOCKER_LOGIN and DOCKER_PASSWORD under repo settings and for account too. I even left them insecure and still get error

[Optimum-Web]

oh, it should be DOCKER_USER,  sorry, now it worked out !

[Jason Dobyns]

I am seeing this issue with the Bitbucket provided bitbucket-piplines.yml docker template.......

[Nick Doyle]

Yeah it uses the long param versions when short are required:

change docker login --username xx --password yyy

to

docker login -u xx -p yyy

[Mohit Gupta]

I was facing the same, so I just login from terminal using administrator privileges and it worked !...

Thanks