Docker Community Forums

Share and learn in the Docker community.

Docker Swarm Services Slow When Browsing via URL

Hi All,

To preface this, I’m relatively new to Docker so excuse anything that does not make sense. We have a docker swarm running Ubuntu 18.04 VMs with 3 Master nodes and 5 Worker nodes (Running about 150 containers between them). Over the past few weeks, we have noticed that the services are super slow to browse when using the URL to the container. When using the direct IPaddress:port provided in UCP, the pages load almost instantly. This leads me to believe that somehow the docker “internal dns” is slow. Below is a sample of how we expose the port and create the URL in the Docker Compose Template for the services:

– com.docker.ucp.mesh.http.80=internal_port=8080,external_route=Internal URL

I’ve done a docker system prune on all of the hosts, I’ve removed all “Created” and “Exited” containers to reduce overhead, restarted the Layer 7 routing, removed stopped containers under individual networks, and have rebooted all of the hosts but the slowness persists. Has anyone experienced this and managed to restore performance to the swarm? Thanks in advance for any help.

Docker Version:
Client: Docker Enterprise Edition (EE) 2.0
Version: 17.06.2-ee-16
API version: 1.30
Go version: go1.8.7
Git commit: 9ef4f0a
Built: Thu Jul 26 16:41:28 2018
OS/Arch: linux/amd64

Server: Docker Enterprise Edition (EE) 2.0
Version: 17.06.2-ee-16
API version: 1.30 (minimum version 1.12)
Go version: go1.8.7
Git commit: 9ef4f0a
Built: Thu Jul 26 16:40:18 2018
OS/Arch: linux/amd64
Experimental: false

Docker Info on one of the Master nodes:

Containers: 23
Running: 21
Paused: 0
Stopped: 2
Images: 1097
Server Version: 17.06.2-ee-16
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 844
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: active
NodeID: aitfommf1vjqdk8wbph94ietl
Is Manager: true
ClusterID: kwluncl403ha8aw6je8a0k46f
Managers: 3
Nodes: 8
Task History Retention Limit: 3
Snapshot Interval: 10000
Number of Old Snapshots to Retain: 0
Heartbeat Tick: 1
Election Tick: 10
Heartbeat Period: 5 seconds
CA Configuration:
Expiry Duration: 3 months
Force Rotate: 0
External CAs:
Root Rotation In Progress: false
Node Address:
Manager Addresses:
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 6e23458c129b551d5c9871e5174f6b1b7f6d1170
runc version: 462c82662200a17ee39e74692f536067a3576a50
init version: 949e6fa
Security Options:
Profile: default
Kernel Version: 4.15.0-32-generic
Operating System: Ubuntu 18.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 31.37GiB
Name: lnk-dq-dockm403
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Experimental: false
Insecure Registries:
Live Restore Enabled: false

Consider this a non-issue. It appears to have been a problem with accessing the services over a slow VPN connection.