Wildfire running on swarm-master #125
Comments
|
When addressing this, you may want to re-read this chain of comments: docker-archive/classicswarm#771 |
|
Waiting for docker/machine#2302 to be resolved |
chscorpio
added a commit
to chscorpio/docker-java
that referenced
this issue
Dec 15, 2015
…n as the token-based swarm-master we create there will conflict with the one we create in docker-swarm. arun-gupta#135 and arun-gupta#136 - In docker-swarm, I provided a command and example output to explain how a master has both a swarm-agent and swarm-agent-master container and followed that example with an explicit step to connect to the swarm cluster. - In docker-swarm, I explicitly required that we connect to the Swarm cluster before verifying that Wildfly and Couchbase are running because we just finished listing the network interfaces on swarm-node-02. - In docker-swarm, I added a sentence to take note which nodes were running Wildfly and Couchbase as they will need to be replaced accordingly in subsequent commands. arun-gupta#125 and arun-gupta#139 - Otherwise, I fixed typos and grammatical errors as I encountered them.
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the
Deploy Java EE Application to Docker Swarm Clustersection, the instructions have the wildfly application deploy to the swarm-master node. You mentioned this is likely happening because the recent Docker Swarm upgrade to 1.0.The text was updated successfully, but these errors were encountered: