{"id":3523,"date":"2019-02-07T07:00:10","date_gmt":"2019-02-07T01:30:10","guid":{"rendered":"http:\/\/www.upnxtblog.com\/?p=3523"},"modified":"2020-04-23T12:28:22","modified_gmt":"2020-04-23T06:58:22","slug":"docker-tutorial-build-docker-image-for-your-database-application","status":"publish","type":"post","link":"https:\/\/www.upnxtblog.com\/index.php\/2019\/02\/07\/docker-tutorial-build-docker-image-for-your-database-application\/","title":{"rendered":"Docker tutorial – Build Docker image for your Database application"},"content":{"rendered":"
<\/div>

Docker<\/strong> as we know, is an open platform for developers and sysadmins to build, ship, and run distributed applications, whether on laptops, data center VMs, or the cloud. In this post, we are going to take look at how to build a Docker image for Database application.<\/p>\n\n

Step #1. Setup Docker<\/h2>\n
    \n
  1. From the docker site, install the latest version of the docker for your platform<\/a>. Docker is available in two editions: Community Edition (CE) and Enterprise Edition (EE). Docker Community Edition (CE) is ideal for developers and small teams looking to get started with Docker and experimenting with container-based apps. Docker Enterprise Edition (EE) is designed for enterprise development and IT teams who build, ship, and run business-critical applications in production at scale.<\/li>\n
  2. Once the installation of docker is over, check the installation by running following command docker run hello-world<\/em>:\n

    \"Validate
    Image – Validate Docker Installation<\/figcaption><\/figure><\/li>\n
  3. Run docker –version<\/em> to check the version of the docker you\u2019re running.\n

    \"Check
    Image – Check Docker version<\/figcaption><\/figure><\/li>\n<\/ol>\n

    OK, now we have got the docker setup, the next step is to define the docker container.<\/p>\n

    Step #2. Create Dockerfile for our container<\/h2>\n
      \n
    1. \n
        \n
      1. Dockerfile will define what goes on in the environment inside the container. Access to resources like networking interfaces and disk drives is virtualized inside this environment, which is isolated from the rest of the system, so you have to map ports to the outside world, and be specific about what files you want to \u201ccopy in\u201d to that environment. So that you can expect that the build of your app defined in this Dockerfile will behave exactly the same wherever it runs.<\/li>\n
      2. Common Dockerfile instructions start with RUN, ENV, FROM, MAINTAINER, ADD, and CMD, among others.\n