Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proxy container will not be reload #209

Open
bewessels opened this issue Nov 20, 2016 · 1 comment
Open

Proxy container will not be reload #209

bewessels opened this issue Nov 20, 2016 · 1 comment

Comments

@bewessels
Copy link

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:
- 8080
volumes:
- ./config.toml:/etc/interlock/config.toml
- /var/run/docker.sock:/var/run/docker.sock

haproxy:
    image: haproxy:latest
    ports:
        - 8080:80
    labels:
        - "interlock.ext.name=haproxy"
    links:
        - interlock:interlock
    depends_on:
        - interlock

app:
    image: ehazlett/docker-demo:latest
    ports:
        - 8080
    labels:
        - "interlock.hostname=saft"
        - "interlock.domain=macsbone.net"
    depends_on:
        - haproxy

`

`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
Copy link
Owner

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants