{"id":104,"date":"2026-09-08T12:00:00","date_gmt":"2026-09-08T07:00:00","guid":{"rendered":"https:\/\/example.com\/?p=104"},"modified":"2026-09-08T12:00:00","modified_gmt":"2026-09-08T07:00:00","slug":"docker-for-beginners","status":"publish","type":"post","link":"https:\/\/www.nexooraclub.com\/?p=104","title":{"rendered":"Docker for Beginners: Containerize Your First App in 15 Minutes"},"content":{"rendered":"\n

Every developer has heard it \u2014 or said it: “But it works on my machine!”<\/em> Different operating systems, library versions and settings make software behave differently from one computer to the next.<\/p>\n\n\n\n

Docker<\/strong> solves this by packaging your app together with everything it needs into a container<\/strong> that runs the same way everywhere: your laptop, a teammate’s PC or a cloud server.<\/p>\n\n\n\n

Containers vs virtual machines<\/h2>\n\n\n\n
<\/th>Virtual machine<\/th>Container<\/th><\/tr><\/thead>
Includes<\/td>A full operating system<\/td>Just your app and its dependencies<\/td><\/tr>
Size<\/td>Gigabytes<\/td>Often tens of megabytes<\/td><\/tr>
Start-up time<\/td>Minutes<\/td>Seconds or less<\/td><\/tr>
Isolation<\/td>Very strong<\/td>Strong (shares the host kernel)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Containers are lightweight because they share the host’s operating system kernel instead of booting their own.<\/p>\n\n\n\n

Key terms in 30 seconds<\/h2>\n\n\n\n
    \n
  • Image<\/strong> \u2014 a read-only template (like a recipe) containing your app and its environment<\/li>\n\n\n
  • Container<\/strong> \u2014 a running instance of an image (the meal cooked from the recipe)<\/li>\n\n\n
  • Dockerfile<\/strong> \u2014 a text file with the instructions to build an image<\/li>\n\n\n
  • Registry<\/strong> \u2014 a place to store and share images, such as Docker Hub<\/li>\n<\/ul>\n\n\n\n

    Step 1: Install Docker<\/h2>\n\n\n\n

    Download Docker Desktop<\/strong> for Windows or macOS from docker.com, or install Docker Engine on Linux. Then check it works:<\/p>\n\n\n\n

    docker --version\ndocker run hello-world<\/code><\/pre>\n\n\n\n
    If you see a “Hello from Docker!” message, you’re ready.<\/p>\n\n\n\n
    Step 2: A tiny app to containerize<\/h2>\n\n\n\n
    Create a folder with a simple Node.js server, server.js<\/code>:<\/p>\n\n\n\n
    const http = require(\"http\");\n\nhttp.createServer((req, res) => {\n  res.end(\"Hello from inside a container! 🐳\");\n}).listen(3000, () => console.log(\"Listening on port 3000\"));<\/code><\/pre>\n\n\n\n
    And a minimal package.json<\/code>:<\/p>\n\n\n\n
    {\n  \"name\": \"hello-docker\",\n  \"version\": \"1.0.0\",\n  \"main\": \"server.js\",\n  \"scripts\": { \"start\": \"node server.js\" }\n}<\/code><\/pre>\n\n\n\n
    Step 3: Write the Dockerfile<\/h2>\n\n\n\n
    # Start from an official, small Node.js image\nFROM node:22-alpine\n\n# Work inside \/app in the container\nWORKDIR \/app\n\n# Copy dependency files first (better caching)\nCOPY package*.json .\/\nRUN npm install --omit=dev\n\n# Copy the rest of the code\nCOPY . .\n\nEXPOSE 3000\nCMD [\"npm\", \"start\"]<\/code><\/pre>\n\n\n\n
    Copying package.json<\/code> before the rest of your code means Docker can reuse the cached npm install<\/code> layer when only your code changes. Builds become dramatically faster.<\/p>\n\n\n\n
    Step 4: Build and run<\/h2>\n\n\n\n
    docker build -t hello-docker .\ndocker run -p 3000:3000 hello-docker<\/code><\/pre>\n\n\n\n
    Open http:\/\/localhost:3000 and you’ll see your message. The -p 3000:3000<\/code> flag maps port 3000 on your computer to port 3000 inside the container.<\/p>\n\n\n\n
    Useful commands to know:<\/p>\n\n\n\n
    docker ps                 # list running containers\ndocker stop <id>          # stop a container\ndocker images             # list images\ndocker logs <id>          # see a container's output<\/code><\/pre>\n\n\n\n
    Step 5: Multi-container apps with Docker Compose<\/h2>\n\n\n\n
    Real apps need more than one service \u2014 say, a web app and a database. Docker Compose<\/strong> describes them all in one file, compose.yaml<\/code>:<\/p>\n\n\n\n
    services:\n  web:\n    build: .\n    ports:\n      - \"3000:3000\"\n    environment:\n      DATABASE_URL: postgres:\/\/app:secret@db:5432\/app\n    depends_on:\n      - db\n\n  db:\n    image: postgres:16\n    environment:\n      POSTGRES_USER: app\n      POSTGRES_PASSWORD: secret\n      POSTGRES_DB: app\n    volumes:\n      - db-data:\/var\/lib\/postgresql\/data\n\nvolumes:\n  db-data:<\/code><\/pre>\n\n\n\n
    Start everything with a single command:<\/p>\n\n\n\n
    docker compose up<\/code><\/pre>\n\n\n\n
    Notice the web app reaches the database at the hostname db<\/code> \u2014 Compose creates a private network where services find each other by name. The db-data<\/code> volume keeps your data safe when containers restart.<\/p>\n\n\n\n
    Never commit real passwords in compose.yaml<\/code>. Use an .env<\/code> file (added to .gitignore<\/code>) or your platform’s secrets manager.<\/p>\n\n\n\n
    Where to go next<\/h2>\n\n\n\n
      \n
    • Add a .dockerignore<\/strong> file to keep node_modules<\/code> and .git<\/code> out of your image<\/li>\n\n\n
    • Learn multi-stage builds<\/strong> to make production images even smaller<\/li>\n\n\n
    • Push your image to a registry and deploy it to a cloud service<\/li>\n<\/ul>\n\n\n\n
      Containers are now the standard way to ship software. Once you’ve containerized one app, you’ll want to containerize everything.<\/p>\n","protected":false},"excerpt":{"rendered":"
      “It works on my machine” is no longer an excuse. Learn what containers are, write your first Dockerfile and run a full app with Docker Compose.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[10,17,18,34],"class_list":["post-104","post","type-post","status-publish","format-standard","hentry","category-cloud-devops","tag-beginners","tag-devops","tag-docker","tag-tutorial"],"_links":{"self":[{"href":"https:\/\/www.nexooraclub.com\/index.php?rest_route=\/wp\/v2\/posts\/104","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.nexooraclub.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.nexooraclub.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.nexooraclub.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.nexooraclub.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=104"}],"version-history":[{"count":0,"href":"https:\/\/www.nexooraclub.com\/index.php?rest_route=\/wp\/v2\/posts\/104\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.nexooraclub.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=104"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.nexooraclub.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=104"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.nexooraclub.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=104"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}