Install Docker In Ec2

To install a software package from the Extras Library, first confirm that the amazon-linux-extras repository is installed on your instance. Then, list the available software packages, enable the one you're looking for, and then install the package using yum. Note: This resolution is for Amazon Linux 2. These steps don't apply to Amazon Linux 1. Docker is making it easier than ever to develop containers on, and for Arm servers and devices. Using the standard tooling and processes you are already familiar with you can start to build, push, pull, and run images of different architectures. No changes to Dockerfiles or source code is needed to start building for Arm. If you are using or upgrading from a version prior to GitLab Runner 10, read how to upgrade to the new version.If you want to install a version prior to GitLab Runner 10, visit the old docs.

Install Docker Ec2 Terraform

  • Installing GitLab Runner
We provide packages for the currently supported versions of Debian, Ubuntu, Mint, RHEL, Fedora, and CentOS. You may be able to install GitLab Runner as a binary on other Linux distributions.Ec2

Install Docker On Ec2 Linux Ubuntu

DistributionVersionEnd of Life date
DebianstretchJune 2022
DebianbusterJune 2024
UbuntuxenialApril 2021
UbuntubionicApril 2023
UbuntufocalApril 2025
Mintsarah, serena, sonya, sylviaApril 2021
Minttara, tessa, tina, triciaApril 2023
Mintulyana, ulyssaApril 2025
RHEL/CentOS7June 2024
CentOS8December 2021
RHEL8May 2029
Fedora32approx. May 2021
Fedora33approx. Nov 2021


Notice that docker-ce is not installed, but the candidate for installation is from the Docker repository for Ubuntu 20.04 ( focal ). Finally, install Docker: sudo apt install docker-ce. Docker should now be installed, the daemon started, and the process enabled to start on boot. Install Docker 1.13 on AWS via CloudFormation. By Philipp Garbe. January 20, 2017. Docker 1.13 has recently been released and what I realized is that there are no good CloudFormation templates available. So I created my own CloudFormation template which creates an EC2 instance based on Ubuntu AMI and installs Docker. In this quick tutorial, I will show you how to install Docker on AWS EC2 instance and run your first Docker container. 1 — Setup EC2 instance. I already did a tutorial on how to create an EC2 instance, so I won’t repeat it. There are few ways you’ll want to differ from the tutorial. To get Docker running on the AWS AMI you should follow the steps below (these are all assuming you have ssh'd on to the EC2 instance). Update the packages on your instance. ec2-user $ sudo yum update -y. ec2-user $ sudo yum install docker -y. Start the Docker Service. ec2-user $ sudo service docker start.

If you want to use the Docker executor, make sure to install Docker beforeusing GitLab Runner. Read how to install Docker for your distribution.

Installing GitLab Runner

If you are using or upgrading from a version prior to GitLab Runner 10, read howto upgrade to the new version. If you wantto install a version prior to GitLab Runner 10, visit the old docs.

To install GitLab Runner:

  1. Add the official GitLab repository:

  2. Install the latest version of GitLab Runner, or skip to the next step toinstall a specific version:

    Debian buster users should disable skel to preventNo such file or directory Jobfailures
  3. To install a specific version of GitLab Runner:

After completing the step above, a runner should be started and beready to be used by your projects!

Make sure that you read the FAQ section which describessome of the most common problems with GitLab Runner.

APT pinning

A native package called gitlab-ci-multi-runner is available inDebian Stretch. By default, when installing gitlab-runner, that packagefrom the official repositories will have a higher priority.

If you want to use our package, you should manually set the source ofthe package. The best way is to add the pinning configuration file.

If you do this, the next update of the GitLab Runner package - whether it willbe done manually or automatically - will be done using the same source:

Updating GitLab Runner

Simply execute to install latest version:

Manually download packages

You can manually download and install thepackages if necessary.

Disable skel

Introduced in GitLab 12.10.

Sometimes the default skeleton (skel) directorycauses issues for GitLab Runner,and it fails to run a job. When installing GitLab Runner, set the environment variableGITLAB_RUNNER_DISABLE_SKEL to true before you install the package. This will createthe $HOME directory without the files inside of skel:

For example:


Install Docker In Aws Ec2 Windows

Upgrading to GitLab Runner 10

To upgrade GitLab Runner from a version prior to 10.0:

  1. Remove the old repository:

  2. Follow the same steps when installing GitLab Runner,without registering it and using the new repository.

  3. For RHEL/CentOS/Fedora, run:

    If you don’t run the above command, you will be leftwith no service file. Follow issue #2786for more information.

Help & feedback

Edit this pageto fix an error or add an improvement in a merge request.
Create an issueto suggest an improvement to this page.
Show and post commentsto review and give feedback about this page.
Create an issueif there's something you don't like about this feature.
Propose functionalityby submitting a feature request.
Join First Lookto help shape new features.
Feature availability and product trials
View pricingto see all GitLab tiers and features, or to upgrade.
Try GitLab for freewith access to all features for 30 days.
Get Help

If you didn't find what you were looking for,search the docs.

If you want help with something specific and could use community support,post on the GitLab forum.

For problems setting up or using this feature (depending on your GitLabsubscription).

Install Docker Compose On Ec2 Linux

Request supportPlease enable JavaScript to view thecomments powered by Disqus.

Installing Jenkins and Docker in an AWS EC2 Instance

Install Docker In Ec2Install Docker In Ec2

In order to do efficient, modern software development, especially for web applications, it is absolutely necessary to have a system for continuous integration (CI) and continuous delivery (CD). The idea with CI is to continuously integrate working code to the repository so that it can continuously be checked for errors. So, a prerequisite is to be using some sort of test driven development (TDD) method or at least some unit test framework; otherwise there is chance to automatically test for errors when the code is committed to the repository. The best CI systems automate everything after the commit. A developer pushes her code, then the CI systems notices the change and automatically runs the tests. When the application passes all of its test, a continuous delivery system should then automatically put the code into the QA, staging, or testing environment. There can be a lot of steps required to get a decent CI/CD system working, and it can be especially daunting when there is no dedicated DevOps team. So, I created a cheat-sheet for quickly setting up a simple Jenkins CI/CD system on an AWS EC2 instance.

Before proceeding you must have an Amazon Web Services account and be somewhat familiar with AWS.

Create an EC2 Instance

  1. Log in to the AWS console and got to EC2 (Services > Compute > EC2)
  2. Launch an Instance (by clicking the big “Launch Instance” button)
    • Choose an Amazon Machine Image
      • Select Amazon Linux AMI (64-bit)
    • Choose an Instance Type
      • Select t2.micro (in the free tier) for testing
      • Select t2.small (not free tier) when using Docker
    • Configure Instance Details
      • If CodePipeline is needed, then Create a new IAM role which includes the policy AWSCodePipelineCustomActionAccess, if one does not already exist
      • Select the newly created IAM role
      • Leave the remaining options as defaulted, or set according to need
    • Add Storage
    • Tag Instance
    • Configure Security Group
      • Create a security group, if one does not already exist, and make sure it has the following inbound rules
        • HTTP, port 80, (select an appropriate source, not unless you have no other option)
        • Custom TCP Rule, port 8080
        • SSH, port 22
    • Review Instance Launch
    • Create a key to access the instance via SSH (referenced below as SSH_KEY_NAME)
  3. Under Instances > Instances, select the new instance an note its Public DNS name (referenced below as PUBLIC_DNS_NAME)
  4. If test results should be reported in local time rather than UTC time, use the following steps
    • Log in to the instance (open a terminal and type the command listed below)
    • Set the timezone
      • Find the correct timezone in /usr/share/zoneinfo (e.g. /usr/share/zoneinfo/America/New_York)
      • Edit /etc/sysconfig/clock so that it only says ZONE='America/New_York' (or whatever timezone is required)
        • sudo vi /etc/sysconfig/clock
      • sudo ln -sf /usr/share/zoneinfo/America/New_York /etc/localtime
    • This will take effect after the next reboot

Install Docker On Ec2

AWS EC2 Login Commands

Install Jenkins

If you are not already logged in to the instance from changing the timezone above, then log in now (see above).

Install Docker (Amazon EC2 Container Service)

Install Other Tools

If you are using the GitHub plug-in then you should create a key to log in to GitHub

Copy the public key, which was just concatenated onto the screen, and add it to your GitHub keys.

The ssh connection will close while the system reboots, which is fine, we are done with it for now.

Configure Jenkins

After the instance reboots, type PUBLIC_DNS_NAME:8080 (use the Public DNS name from above) into a browser. The Jenkins interface should be seen.

Configure Security Credentials

How To Install Docker In Ec2

  • Manage Jenkins > Setup Security
    • Enable Security
    • Security Realm = Jenkins’ own user database
      • Allow users to sign up
    • Authorization = Matrix based
    • Save
  • Sign up (as administrator) and log in
  • Manage Jenkins > Configure Global security
    • Add all permissions for your account
    • Remove all but read from anonymous
    • Save

Update and Install Plugins

Install plugins which are appropriate for your needs, below are the ones that I use.

  1. Update existing installed plugins using the Jenkins interface
  2. Install the AWS CodePipeline plugin
  3. Install the GitHub plugin
  4. Install the NodeJS plugin
  5. Install the TAP plugin

Jenkins needs to restart after all of the plugins are installed. It can take a while to update some of the existing plugins, so I normally take a break at this point and finish the steps below at a later time.

Finish Jenkins Configuration

GitHub Credentials

If you will be getting code from GitHub, then you will need to tell Jenkins to use the proper ssh key.

  • Jenkins > Manage Jenkins
  • Manage Credentials
  • Add Credentials > SSH Username with Private Key
    • From the Jenkins master ~/.ssh

Jenkins System Configuration

  • Manage Jenkins > Configure System
    • NodeJS
      • Add NodeJS
        • Name the Node installation
        • Install automatically from nodejs.org
        • Select the node version to install (If you do not see a drop-down list of Node version choices, then you may need to restart Jenkins)
        • Global NPM packages to install
          • ember-cli bower phantomjs
    • Jenkins Location
    • E-mail Notification (assuming Gmail)
      • Click advanced
      • SMTP server = smtp.gmail.com
      • CHeck Use SSL
      • SMTP Port = 465
      • Check Use SMTP Authentication
      • User Name = [email protected]
      • Password = ???

Install Docker In Ec2 Windows

Configure Items

With the Jenkins system set up, it is now possible to create build and test processes. The steps required varies based upon which tools are being used, and they will be covered in future posts. The last thing which you may want to do is to go to the EC2 console and save this instance as an image, so that you do not have to go through all of these steps again.


Install Docker In Ec2 Ubuntu


Install Docker-compose In Ec2 Instance


Most Viewed Posts