ehazlett / interlock

Docker Event Driven Plugin System
Apache License 2.0
976 stars 130 forks source link

Proxy container will not be reload #209

Open bewessels opened 7 years ago

bewessels commented 7 years ago

Hi There, im running in an Issue.

When i first start. HAProxy will quit because it didnt find the config. I have to restart the container. Then when i scale the app. Interlock will write the correct config but the haproxy container will not restart. Even here i have to do it by hand.

I dont use Swarm. Its just a simple docker install.

` Client: Version: 1.12.1 API version: 1.24 Go version: go1.6.2 Git commit: 23cf638 Built: Tue, 27 Sep 2016 12:25:38 +1300 OS/Arch: linux/amd64

Server: Version: 1.12.1 API version: 1.24 Go version: go1.6.2 Git commit: 23cf638 Built: Tue, 27 Sep 2016 12:25:38 +1300 OS/Arch: linux/amd64 docker-compose version 1.8.1, build 878cff1 docker-py version: 1.10.3 CPython version: 2.7.9 OpenSSL version: OpenSSL 1.0.1e 11 Feb 2013 `

`version: "2"

services: interlock: image: ehazlett/interlock:1.3.0 command: run -c /etc/interlock/config.toml ports:

`ListenAddr = ":8080" DockerURL = "unix:///var/run/docker.sock"

[[Extensions]] Name = "haproxy" ConfigPath = "/usr/local/etc/haproxy/haproxy.cfg" PidPath = "/var/run/haproxy.pid" TemplatePath = "" BackendOverrideAddress = "172.19.0.1" MaxConn = 1024 Port = 80 AdminUser = "admin" AdminPass = "interlock" `

ehazlett commented 7 years ago

This usually happens if there is an invalid config file. Can you check the logs from the HAProxy container? It should tell the error.