-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Conversation
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
|
||
## Create your hosts | ||
|
||
Here, you create five Linux hosts that are part of the "Docker Swarm Example" security group and install Docker Engine on each one. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it looks like you've moved installing the engine out of "here", and into the next section
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated.
| HTTP | TCP | 80 | 0.0.0.0/0 | Container images | | ||
| Custom TCP Rule | TCP | 2375 | 172.30.0.0/24 | Non-TLS traffic | | ||
| Custom TCP Rule | TCP | 8500 | 172.30.0.0/24 | Consul discovery | | ||
| Custom TCP Rule | TCP | 4000 | 172.30.0.0/24 | Swarm HA managers | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be worth explicitly noting that this network setup means we don't need to secure the Engine, Swarm, and Consul ports, as they're only accessible from within the private network - possibly during the setup steps below.
Someone scanning it may miss it, and we really don't want more unencrypted Docker ports out there (we have way too many already)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not quite sure what you'd like to see done. But I've updated the content.
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
I'm going to carry this PR and then we'll iterate on it tomorrow in a new PR. |
replaced by #1753 , closing. |
Please review this WIP topic. The goal of the topic is to demonstrate a minimal HA Swarm cluster on a VCS. In this case we happen to be using AWS, but I've tried to keep that in the background. I'm having trouble with the following command not returning control to the command line, and would appreciate your help solving that issue.
Your comments and feedback are welcome.
Thanks in advance.
Rolfe