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.

Sign up for GitHub

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

Jump to bottom

haproxy sericve does not run in the swarm mode #244

Open
kiyanabah opened this issue Oct 25, 2017 · 4 comments
Open

haproxy sericve does not run in the swarm mode #244

kiyanabah opened this issue Oct 25, 2017 · 4 comments

Comments

@kiyanabah
Copy link

kiyanabah commented Oct 25, 2017 •
edited
Loading

I have the interlock with haproxy configuration in swarm, interlock service works whereas cant reloads haproxy, i tried restart_policy on the haproxy and also DoNotRestartContainer = 1 in config.toml
@ehazlett
Copy link
Owner

Are you using swarm mode? What version of docker?

@kiyanabah
Copy link
Author

Yes, Docker version 17.09.0-ce.

@ehazlett
Copy link
Owner

Unfortunately Interlock does not yet support Swarm mode. There is a branch in progress.

@sido420
Copy link

sido420 commented Nov 6, 2018

Whats the status of this issue? Has this been released?
It looks like it is only available to Docker EE customers https://docs.docker.com/ee/ucp/interlock/usage/sessions/

ehazlett pushed a commit that referenced this issue Aug 16, 2019
@euanh @ehazlett
test/integration: Remove Windows configuration (#244)
1cfa8d5 
There is no plan to make Interlock run on Windows, so this config file is
not used.   As a result it has fallen out of date and also contains
lint errors.

Signed-off-by: Euan Harris <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ehazlett @kiyanabah @sido420