如何在Docker Swarm中为Swarm集群中的特定容器启用JMX？

问题陈述：我需要通过JMX连接到Docker群服务中的特定容器。 服务没有暴露在任何端口上，所以我不能通过直接打开暴露端口上的docker基板来访问JMX。

另外，在服务暴露的情况下，群集负载平衡并不能保证我打哪个容器。

Answer 1

您可以ssh到运行您的容器的工作节点，从那里你就像在本地机器上一样与容器交互。

如果您使用docker-machine创buildworker节点，您可以使用ssh：

docker-machine ssh <node-name> 

Answer 2

 Able to solve the problem via the following approach: 1. Update service to take a inject a separate environment variable, say JMX_OPTS, while starting the application. 2. Update the docker service to add that environment variable docker service update --env-add JMX_OPTS="-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.rmi.port=7001 -Dcom.sun.management.jmxremote.port=7001 -Dcom.sun.management.jmxremote.authenticate=true -Dcom.sun.management.jmxremote.ssl=false -Djava.rmi.server.hostname=<hostname_IP> -Dcom.sun.management.jmxremote.password.file=/jmxremote.password" service123 You can choose any port number. There is NO need to update dockerfile to EXPOSE the port. Also, in -Djava.rmi.server.hostname, enter the swarm managers IP, and not the hostname. 3. Add another HA Proxy service to connect with the specific container in using swarm network. docker service create --name proxy-docker-service123 --network swarm-net -p 7001:7001 -e "BACKEND_HOST=<CONTAINER_IP>" -e "BACKEND_PORT=7001" demandbase/docker-tcp-proxy CONTAINER_IP can be found by inspecting the command: docker inspect d87c42441faf | grep IPv4 Make sure that for a docker-tcp-proxy all source, target and backend ports are same. For JMX with SSL: Update JMX_OPTS with following parameters docker service update --env-add JMX_OPTS="-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.rmi.port=7001 -Dcom.sun.management.jmxremote.port=7002 -Dcom.sun.management.jmxremote.authenticate=true -Djava.rmi.server.hostname=<hostname_ip> -Dcom.sun.management.jmxremote.password.file=/jmxremote.password -Djavax.net.ssl.keyStore=<location_to_keystore> -Djavax.net.ssl.keyStorePassword=<keyStore_Password> -Dcom.sun.management.jmxremote.ssl.need.client.auth=false -Dcom.sun.management.jmxremote.registry.ssl=true -Dcom.sun.net.ssl.checkRevocation=false" Please note in this case, jmxremote and rmi are running on two separate ports. So, we need to deploy two HA proxy services. One for port 7001 and one for 7002.