Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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

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

Error: Cannot perform an interactive login from a non TTY device

The full yml is:
- step:
- docker build -t s4ysolutions/spartan-resume-server -f docker/server.Dockerfile .
- docker push s4ysolutions/spartan-resume-server
# - docker build -t s4ysolutions/spartan-resume-front -f docker/front.Dockerfile .
#- docker push s4ysolutions/spartan-resume-front
docker: true


5 answers

1 accepted

9 votes
Answer accepted

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...

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

Like # people like this

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.)

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

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

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

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

change docker login --username xx --password yyy


docker login -u xx -p yyy

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

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


0 votes

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

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

2,138 views 2 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you