insecure mode isn't enabled.

[sirwolfgang]

With version 1.0.0 I now get the docker.errors.DockerException: HTTPS endpoint unresponsive and insecure mode isn't enabled. when connecting to my private http repo. I do not see a way to allow/change the behavior to use http.

[dnephin]

#562

For now you can docker pull --allow-insecure-ssl , which I believe should allow fig up, and fig run to succeed.

[bfirsh]

Merged #562. This will be in Fig 1.0.1. :)

[mouadino]

@dnephin I think there were a typo on your command it should be: fig pull --allow-insecure-ssl and not docker ....

Cheers,

[sirwolfgang]

@mouadino he was speaking to the work around until that patch was pushed. But thanks!

[wangzi19870227]

I got same problem (I'm on docker 1.5.0 and fig 1.1.0).

[root@haichuan-vm fig-elk]# docker-compose pull
Pulling elasticsearch (registry.docker.sce.sina.com/deviantony/elk-elasticsearch:latest)...
Traceback (most recent call last):
  File "<string>", line 3, in <module>
  File "/code/build/docker-compose/out00-PYZ.pyz/compose.cli.main", line 31, in main
  File "/code/build/docker-compose/out00-PYZ.pyz/compose.cli.docopt_command", line 21, in sys_dispatch
  File "/code/build/docker-compose/out00-PYZ.pyz/compose.cli.command", line 27, in dispatch
  File "/code/build/docker-compose/out00-PYZ.pyz/compose.cli.docopt_command", line 24, in dispatch
  File "/code/build/docker-compose/out00-PYZ.pyz/compose.cli.command", line 59, in perform_command
  File "/code/build/docker-compose/out00-PYZ.pyz/compose.cli.main", line 231, in pull
  File "/code/build/docker-compose/out00-PYZ.pyz/compose.project", line 197, in pull
  File "/code/build/docker-compose/out00-PYZ.pyz/compose.service", line 523, in pull
  File "/code/build/docker-compose/out00-PYZ.pyz/docker.client", line 824, in pull
  File "/code/build/docker-compose/out00-PYZ.pyz/docker.auth.auth", line 67, in resolve_repository_name
  File "/code/build/docker-compose/out00-PYZ.pyz/docker.auth.auth", line 46, in expand_registry_url
docker.errors.DockerException: HTTPS endpoint unresponsive and insecure mode isn't enabled.

following cmd work for me:
docker-compose up --allow-insecure-ssl

[yoanisgil]

Same issue here. I ran docker-compose up and got:

Recreating root_zabbix_1...
Creating root_influxdb_1...
Pulling image docker.io/tutum/influxdb:latest...
Traceback (most recent call last):
  File "<string>", line 3, in <module>
  File "/code/build/docker-compose/out00-PYZ.pyz/compose.cli.main", line 31, in main
  File "/code/build/docker-compose/out00-PYZ.pyz/compose.cli.docopt_command", line 21, in sys_dispatch
  File "/code/build/docker-compose/out00-PYZ.pyz/compose.cli.command", line 27, in dispatch
  File "/code/build/docker-compose/out00-PYZ.pyz/compose.cli.docopt_command", line 24, in dispatch
  File "/code/build/docker-compose/out00-PYZ.pyz/compose.cli.command", line 59, in perform_command
  File "/code/build/docker-compose/out00-PYZ.pyz/compose.cli.main", line 464, in up
  File "/code/build/docker-compose/out00-PYZ.pyz/compose.project", line 208, in up
  File "/code/build/docker-compose/out00-PYZ.pyz/compose.service", line 214, in recreate_containers
  File "/code/build/docker-compose/out00-PYZ.pyz/compose.service", line 197, in create_container
  File "/code/build/docker-compose/out00-PYZ.pyz/docker.client", line 710, in pull
  File "/code/build/docker-compose/out00-PYZ.pyz/docker.auth.auth", line 67, in resolve_repository_name
  File "/code/build/docker-compose/out00-PYZ.pyz/docker.auth.auth", line 46, in expand_registry_url
docker.errors.DockerException: HTTPS endpoint unresponsive and insecure mode isn't enabled.

However this command did work (notice I did not need to pass --allow-insecure-ssl):

docker pull docker.io/tutum/influxdb:latest

I'm running docker 1.6.0 On CentOS7.:

[root@aws034 ~]# docker -v
Docker version 1.6.0, build 8aae715/1.6.0

[whitney-beck]

I'm experiencing the same thing as @yoanisgil. --insecure-registry is configured in the docker daemon.

[smboykin]

I'm also experiencing the same as @whitney-beck and @yoanisgil, I'm trying to pull from a private registry. docker pull works, but docker-compose up does not

[aanand]

Fixed by #1736 and released in Compose 1.4.0 RC2.

[alexeyOnGitHub]

I tried both Compose 1.3.x and 1.4.0RC2.
it still cannot load data from private HTTPS site. if I add "--insecure-registry mysitehere", then it prints out help text and does not seem to accept the parameter.

[yoanisgil]

@alexeyOnGitHub can you share your docker version as well as the traceback? That might help others to help you figuring out what the issue is ;) or even try to reproduce the problem.

[alexeyOnGitHub]

@yoanisgil , thank you for getting back to me. I'm sorry, I was in a hurry and didn't provide more details hoping that maybe it was a known issue already.
here is the output: https://gist.github.com/alexeyOnGitHub/7903076e81fd9aedda96

this is on MacOS 10.

[yoanisgil]

@alexeyOnGitHub I don't think this ticket refers to the same issue you're facing. Actually if you take a look at docker-compose up --help and you will see there is no such option --insecure-registry for the up command, which is why you get the command's documentation. Also make sure you run docker login before asking compose to launch your services.