I have been on and off with Docker, so my knowledge of Docker is a bit rusty… According to the 1.12 release notes, Swarm is now baked in the engine itself (great!) Swarm allows for intelligent re-routing of network traffic depending on the health of the docker nodes. Question: 99% of the enterpr…

Here is the article that made me ask this question: [image] Docker Swarm Is Dead. Long Live Docker Swarm. At DockerCon, Docker released version 1.12 of the core product, Docker Engine. The biggest new feature is that Docker Swarm is no longer a separate tool - now it's built into Docker …

I would love more info on this very question. I’ve played around with a local swarm created via docker-machine. I’ve been able resolve dns for a specific service but only from within another container(on the same network mess). What is the best way to expose these services without static host to …

In 1.12, --publish of docker service will expose a “Swarm port” on all hosts for that service. This “Swarm port” is a port which gets NATed to a Virtual IP address for each service “task” (container, in this case) using the Linux kernel’s built-in load balancing functionality, IPVS . This is a OSI …

e.g., on a docker manager running Swarm mode: $ docker service create --name appservers --publish 30000:80 nginx 9ji18cicp7da3nenc2l9kwtb5 $ docker service update --replicas 3 appservers appservers $ docker service ls ID NAME REPLICAS IMAGE COMMAND 9ji18cicp7da appservers 3/…

This is good stuff and is essentially what I have been doing in my local sandbox, but I’m still not clear on some things. [image] nathanleclaire: If your HAproxy service instance is on an overlay network with the service(s) that it is directing requests to, you can simply point towards the DNS …

[image] reppard: In this scenario, how is HAproxy dynamically configured to route traffic to new services? It wouldn’t be today. But you could route to service name via DNS, so the re-write config / reload HAProxy loop is probably much less frequent (per-service vs. per-container). Being spe…

We create our own L4 lb with native docker and swarm api support . it add /delete containers from balancing pool by discovering them via swarm with arguments : internal port and label simple config looks like: [servers.sample3] bind = "50.50.50.50:80" protocol = "tcp" balance = “weight” [serv…

I’ve had a go at solving this problem without the need for any config or an instance of HAProxy/Nginx with dynamic config generation. Using the list of services and a few labels I’ve written a service which will route DNS names (and optionally decrypt TLS also provided via labels) to the VIP for a s…

How Swarm 1.12 support websockets?

Docker 1.12 swarm still needs http (reverse) proxy?

General

fsckdevhdb8 (Fsckdevhdb8) June 29, 2016, 7:50pm 2

I’d like to know too

Swarm mode VIP without HAProxy using VIPs?

Topic		Replies	Views
Registering Docker 1.12 Swarm services in Consul General	17	15183	August 10, 2017
Load balancing in 1.12 Swarm	13	5044	January 10, 2017
Service discovery in Swarm (>1.12) Swarm	4	3796	February 7, 2017
How to configure Swarm Service Discovery (1.12) Swarm	38	13159	February 9, 2017
HAProxy load balancer outside the swarm, how? Swarm	3	4709	September 22, 2023

Docker 1.12 swarm still needs http (reverse) proxy?

Related topics