The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How can we find where to configure the Docker_username and docker_password.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am seeing this issue with the Bitbucket provided bitbucket-piplines.yml docker template.......
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Changing `--username` to `-u` and `--password` to `-p` did the trick. Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I was facing the same, so I just login from terminal using administrator privileges and it worked !...
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
==
+ 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