How to set docker --insecure-registry property as part of Bitbucket pipeline job

[Oliver Bradonjic]

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

{
"insecure-registries": ["myIP:myPORT"]
}

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?

Thanks

BR.

Oliver

[lassian]

I have created a feature request for this in bitbucket, please add your comments to it regarding adding support for this.

https://bitbucket.org/site/master/issues/17946/allow-users-to-configure-insecure-docker

[Sven Weber]

Is there any solution on insecure registries yet?

[julien-seed]

Up

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.

It's possible?

Thanks. BR