arnoldst
commented
7 years ago Ok - after more digging I suspect I know whats going on. Bluemix's docker host url is tcp://containers-api.eu-gb.bluemix.net:8443. Which is https.
So I'm guessing the registrator uses http by default.
So I think the question is - how to get the registrator to talk https to the docker host ???
Server: Version: 3.0 API version: 1.20 (minimum version ) Go version:
Git commit:
Built: Mon Jun 26 22:20:15 2017 OS/Arch: Bluemix Containers/ Experimental: false
What version of registrator are you running? v7
Did you build a custom version of registrator? If so, what is that image? no - just grabbed latest from docker hub
What is the exact command you are running registrator with? docker --debug run -d -e DOCKER_HOST=tcp://containers-api.eu-gb.bluemix.net:8443 --name registrator -h registrator --volume docker.sock:/tmp/docker.sock --link consul:consul.example registry.eu-gb.bluemix.net/honeybee/registrator:latest -internal consul://consul.example:8500
What is the exact command you are running your container with? See above
A log capture of all the docker events before, during, and after the issue. Starting registrator v7 ... Q2017/06/27 09:04:24 Using consul adapter: consul://consul.dataswarm.example:8500 02017/06/27 09:04:24 Connecting to backend (0/0)
If relevant,
Dockerfilefor application that is having issues.Description of the problem: I'm trying to run consul and registartor on IBM Bluemix. So its a remote docker engine.
How reproducible: Ever time.
Steps to Reproduce: Log into bluemix ( bx login), bx ic init, then set the following environment properties export DOCKER_HOST=tcp://containers-api.eu-gb.bluemix.net:8443 export DOCKER_CERT_PATH=/Users/steve/.ice/certs/containers-api.eu-gb.bluemix.net/48b3fe26-09e7-4bc4-bdc5-6c4686fd22f2 export DOCKER_TLS_VERIFY=1
Actual Results: container just shuts down.
Expected Results:
Additional info: It would be good to know what the cotnainer is trying to do after it says Listening for Docker events.