Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
Hi to all,
I am running pipeline job which push docker image to our private docker registry.
Docker registry is not running over https and to push image from my local computer I add this line
to "etc/docker/deamon.json file and it works how I expect.
But when run pipeline job I got this error
Error response from daemon: Get https://myIP:myPORT/v1/users/: http: server gave HTTP response to HTTPS client
This is our bitbucket-pipelines.yaml file
image: maven:3.3.9-jdk-8 options: docker: true pipelines: branches: master: - step: script: - mvn -s settings.xml clean deploy # -B batch mode makes Maven less verbose develop: - step: script: - mvn -s settings.xml clean deploy # -B batch mode makes Maven less verbose - docker login myIP:myPORT -u $NEXUS_USERNAME -p $NEXUS_PASSWORD - docker build -t myService:1.0-SNAPSHOT . - docker push myIP:myPORT/myService:1.0-SNAPSHOT
How can I set insecure-registries property?
Hi to all,
i have exactly the same question. I make a rapid test to etablish a connexion between a pipeline bitbucket and a private docker registry.
That work with different machine if i had --insecure option and i try to do the same with bitbucket.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs