toolshed/docker-cli
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update basic setup instructions

Browse Source 
Without adding the user to the group you're going to hit nasty TLS errors. Figured I'd save the next guy the hassle.

Problem more accurately described here:
https://github.com/docker/docker/issues/5314

Signed-off-by: Jason Divock <jdivock@box.com>
Upstream-commit: 25d07511ed63959777ab1d0bee9f8e5f79382318
Component: engine
This commit is contained in:
Jason Divock
2015-04-14 16:56:34 -07:00
committed by Jason Divock
parent 0d57506a8e
commit 95380313e0
1 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
components/engine/docs/sources/installation/amazon.md
+6 -2
View File
@@ -28,8 +28,12 @@ Repository.
your Amazon Linux instance should be running!
3. SSH to your instance to install Docker :
`ssh -i <path to your private key> ec2-user@<your public IP address>`
4. Once connected to the instance, type
`sudo yum install -y docker ; sudo service docker start`
4. Add the ec2-user to the docker group :
`sudo usermod -a -G docker ec2-user`
5. Restart the machine and log back in
`sudo shutdown -r now`
6. Once connected to the instance, type
`sudo yum install -y docker ; sudo service docker start`
to install and start Docker
**If this is your first AWS instance, you may need to set up your Security Group to allow SSH.** By default all incoming ports to your new instance will be blocked by the AWS Security Group, so you might just get timeouts when you try to connect.