The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

s4y
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 9, 2017
 
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

 

5 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

12 votes
Answer accepted
TPaz
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 27, 2017

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
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 19, 2020

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

Like # people like this
RLogik
Contributor
October 3, 2020

I set up these values, and obtain a

denied: requested access to the resource is denied

in my pipeline. Any ideas? (In DockerHub have already connected my Bitbucket acct.)

3 votes
Optimum-Web
November 30, 2017

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

 

 

Screen Shot 2017-11-30 at 21.10.21.png

Optimum-Web
November 30, 2017

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

2 votes
Jason Dobyns
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 20, 2017

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

Nick Doyle
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 23, 2018

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

Marco Araujo
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 21, 2020

Changing  `--username` to `-u` and `--password` to `-p` did the trick. Thanks.

1 vote
Mohit Gupta
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 20, 2020

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

Thanks

0 votes
Kong Kunru
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 16, 2022

I just had this problem, I managed to get round it by piping in the password and using --password-stdin attribute.

 

echo $DOCKER_PASSWORD | docker login -u $DOCKER_USERNAME --password-stdin

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

TAGS
AUG Leaders

Atlassian Community Events