Docker Exec: Accessing Running Containers

🐳 Docker Commands Explained: run, ps, and stop (with Nginx) When you start learning Docker, there are three commands that form the foundation of almost everything you'll do: • docker run — start a container • docker ps — see running containers • docker stop — stop a container safely If you understand these three, you already understand the basic lifecycle of a container. In this beginner-friendly guide, we walk through these commands step by step using a real example with Nginx, so you can actually see a container running in your browser. Inside the tutorial you’ll learn: • What happens when you run docker run nginx • Why containers sometimes block your terminal • How -d, -p, and --name flags work • How to check running containers with docker ps • The right way to stop containers using docker stop 📖 Read the full tutorial: https://lnkd.in/gdNX7UHX 💡 After learning the basics, the best way to truly understand Docker is by practicing with real containers. You can register on Docker HOL and explore hands-on Docker labs designed for students, beginners, and developers. ✔ Practical Docker exercises ✔ Real command-line workflows ✔ Step-by-step container labs 🔗 Start learning Docker: https://dockerhol.com #Docker #DevOps #LearnDocker #DockerCommands #Containerization #DockerTutorial

🐳 What is Docker? A Beginner’s Guide to Containerization If you're starting with Docker, you've probably heard developers say: "But it works on my machine!" Environment issues, dependency conflicts, and inconsistent deployments are common problems in software development. Docker solves this by packaging applications and their dependencies into portable containers that run the same everywhere. In this beginner-friendly tutorial, you’ll learn: • What Docker is and why it matters • Containers vs Virtual Machines • Docker Images and Containers explained • How Docker solves environment problems • A simple example to run your first container 📖 Read the full tutorial: https://lnkd.in/ghpga8eB 💡 Want to practice Docker instead of just reading about it? You can register on Docker HOL and start learning through hands-on labs designed for students, beginners, and developers. ✔ Interactive Docker labs ✔ Real commands and practical exercises ✔ Step-by-step learning path ✔ Built for beginners who want real experience 🔗 Start learning Docker: https://dockerhol.com #Docker #Containerization #DevOps #DockerTutorial #LearnDocker #CloudComputing

Day 12/30 – Docker Learning Series Docker Exec and Interactive Containers Today I explored how to interact with running containers, which is an essential skill for debugging and managing applications in Docker. Running a container is not always enough. In real-world scenarios, we often need to go inside a container to inspect files, check processes, or troubleshoot issues. --- What is docker exec? The docker exec command is used to run commands inside a running container. Basic syntax: docker exec <container_id> <command> --- Open Interactive Terminal Inside a Container docker exec -it <container_id> /bin/bash Explanation: -i → Interactive mode -t → Allocates a terminal /bin/bash → Opens a shell inside the container If bash is not available (like in Alpine images), use: docker exec -it <container_id> /bin/sh --- Example Run an Nginx container: docker run -d --name mynginx nginx Enter the container: docker exec -it mynginx /bin/bash Now you are inside the container and can run Linux commands. --- Run One-Time Commands Inside Container docker exec mynginx ls /usr/share/nginx/html This runs a command without opening a full terminal. --- What are Interactive Containers? Interactive containers allow you to interact directly with the container’s shell. Example: docker run -it ubuntu /bin/bash This starts a container and immediately opens a terminal. --- Exit from Container Type: exit This will close the container session. --- Key Takeaways • docker exec allows access to running containers • Useful for debugging and inspecting applications • Interactive mode helps simulate real server environments • Essential skill for troubleshooting in DevOps Being able to enter and inspect containers is critical when working with production systems. --- Day 12/30 – Docker Learning Series Next: Dockerfile Introduction and Writing Your First Dockerfile #Docker #DevOps #Containerization #CloudComputing #CICD #Infrastructure #SRE #LearningInPublic #TechLearning #NetworkToDevOps

🚀 Understanding What Happens Inside a Dockerfile (Step-by-Step) Many people start using Docker by simply running containers. But the real magic happens inside a Dockerfile — the blueprint that tells Docker how to build your application environment. Think of a Dockerfile like a recipe. Each instruction runs step-by-step and builds the final container image. Let’s understand the actual order Docker follows while building an image. 📦 1️⃣ FROM – The Starting Point Every Docker image begins with a base image. Example: FROM ubuntu:22.04 This tells Docker to start building the container using Ubuntu as the foundation. 📂 2️⃣ WORKDIR – Set Working Directory Defines where the application will run inside the container. Example: WORKDIR /app All upcoming instructions will run inside this directory. 🌐 3️⃣ ENV – Environment Variables Used to store configuration values. Example: ENV NODE_ENV=production Applications inside the container can use these variables. 📁 4️⃣ COPY / ADD – Add Application Files Copies files from your system into the container. Example: COPY . . COPY is commonly used, while ADD has some extra capabilities like extracting archives. ⚙️ 5️⃣ RUN – Install Dependencies Executes commands during the image build. Example: RUN apt-get update && apt-get install -y python3 This prepares everything the application needs before it runs. 🌐 6️⃣ EXPOSE – Declare Application Port Example: EXPOSE 3000 This documents which port the application inside the container will use. 🚀 7️⃣ ENTRYPOINT – Main Execution Command Defines the main command that always runs when the container starts. Example: ENTRYPOINT ["python3"] ▶️ 8️⃣ CMD – Default Command Provides default arguments or commands. Example: CMD ["app.py"] If no command is provided while running the container, Docker uses CMD. 💡 In simple terms A Dockerfile tells Docker: Start with a base image → set a working folder → define variables → copy files → install dependencies → declare ports → define how the container runs. That’s how a Docker image becomes production ready. 💬 DevOps engineers: Which Dockerfile instruction do you use the most? #Docker #Containerization #DevOps #CloudComputing #TechLearning #SoftwareEngineering

🚀 Understanding What Happens Inside a Dockerfile (Step-by-Step) Many people start using Docker by simply running containers. But the real magic happens inside a Dockerfile — the blueprint that tells Docker how to build your application environment. Think of a Dockerfile like a recipe. Each instruction runs step-by-step and builds the final container image. Let’s understand the actual order Docker follows while building an image. 📦 1️⃣ FROM – The Starting Point Every Docker image begins with a base image. Example: FROM ubuntu:22.04 This tells Docker to start building the container using Ubuntu as the foundation. 📂 2️⃣ WORKDIR – Set Working Directory Defines where the application will run inside the container. Example: WORKDIR /app All upcoming instructions will run inside this directory. 🌐 3️⃣ ENV – Environment Variables Used to store configuration values. Example: ENV NODE_ENV=production Applications inside the container can use these variables. 📁 4️⃣ COPY / ADD – Add Application Files Copies files from your system into the container. Example: COPY . . COPY is commonly used, while ADD has some extra capabilities like extracting archives. ⚙️ 5️⃣ RUN – Install Dependencies Executes commands during the image build. Example: RUN apt-get update && apt-get install -y python3 This prepares everything the application needs before it runs. 🌐 6️⃣ EXPOSE – Declare Application Port Example: EXPOSE 3000 This documents which port the application inside the container will use. 🚀 7️⃣ ENTRYPOINT – Main Execution Command Defines the main command that always runs when the container starts. Example: ENTRYPOINT ["python3"] ▶️ 8️⃣ CMD – Default Command Provides default arguments or commands. Example: CMD ["app.py"] If no command is provided while running the container, Docker uses CMD. 💡 In simple terms A Dockerfile tells Docker: Start with a base image → set a working folder → define variables → copy files → install dependencies → declare ports → define how the container runs. That’s how a Docker image becomes production ready. 💬 DevOps engineers: Which Dockerfile instruction do you use the most? #Docker #Containerization #DevOps #CloudComputing #TechLearning #SoftwareEngineering

Docker — What I've learned so far: Most beginners confuse containers with images. Here's the simplest way to understand it: → Image = Blueprint → Container = A running instance of that blueprint Once this clicked, everything else started making sense: 1. Containers You don't install apps directly on your machine anymore. You run them inside isolated containers. Clean. Portable. Consistent. 2. Images ↔ Containers You can create an image from a container (docker commit). You can spin up a container from an image (docker run). This two-way flow is what makes Docker powerful. 3. Docker Hub Think of it as GitHub but for Docker images. You push your custom images. You pull others' images. One command and your environment is ready anywhere. 4. Repositories Every image lives inside a repository. Versioning, tagging, organizing — all handled here. Currently also learning Bash scripting alongside Docker because automation without shell scripting is incomplete. Docker handles the "what to run." Bash handles the "how to automate it." Together, they're a solid foundation for anyone stepping into DevOps. Still learning. Still building. #Docker #Bash #DevOps #Linux #Containerization #LearningInPublic

🚀 Day 37/90 — Docker Revision Day Instead of rushing into new tools today, I did something equally important — revision. Over the past few days, I’ve been working deeply with Docker as part of my #90DaysOfDevOps journey. Today I consolidated everything I learned to make sure the fundamentals actually stick. Here’s what I revised today: 🐳 Running and managing containers 🐳 Building and tagging custom images 🐳 Writing Dockerfiles from scratch 🐳 Working with volumes and bind mounts 🐳 Container networking 🐳 Multi-container apps with Docker Compose 🐳 Multi-stage builds and pushing images to Docker Hub To make things easier for future reference, I also created a Docker Commands Cheat Sheet that covers the commands I’ll actually use while working with containers. 📌 Docker Cheat Sheet: One thing I realized today: Learning tools is easy — retaining them requires revision and practice. Also identified a couple of areas to strengthen: • Image layers & caching • CMD vs ENTRYPOINT Small steps every day → building real DevOps skills. #90DaysOfDevOps #DevOps #Docker #LearningInPublic #DevOpsJourney #TrainWithShubham #CloudComputing

🚀 From Learning to Running My First Docker Container Today! 🐳 Today I took another step in my DevOps learning journey by exploring Docker, one of the most widely used tools in modern application deployment. One common challenge developers face is: 👉 It works on my machine, but not on the server. Today I understood how Docker solves this problem by using containers. 💡 What is Docker? Docker is a containerization platform that packages an application along with all its dependencies into a lightweight container, ensuring the application runs consistently across different environments. 📚 Key Concepts I Learned Today 🔹 Docker Image – Blueprint used to create containers 🔹 Docker Container – Running instance of an image 🔹 Dockerfile – Script used to build Docker images 🔹 Docker Hub – Registry to store and share images 🔹 Port Mapping – Connecting the host machine to container services ⚙️ Hands-on Commands I Practiced docker --version docker pull nginx docker images docker run -d -p 8080:80 nginx docker ps docker ps -a docker logs <container_id> docker stop <container_id> docker rm <container_id> 🔗 Practical Experiment I Did I successfully ran an Nginx container and connected it with my host machine using port mapping. After running the container, I accessed it in my browser using: 👉 http://localhost:8080 Seeing the container run successfully and accessing it from the browser was a great hands-on learning experience. #Docker #DevOps #Containerization #LearningInPublic #CloudComputing #TechJourney #FutureDevOpsEngineer

🐳 Docker Desktop Tour — Walk Through Every Section Like Showing a Friend Around You install Docker Desktop… open it… and suddenly see: Containers Images Volumes Settings Logs Stats …and a dashboard full of IDs and green dots. If you’re new to Docker, this interface can feel confusing at first. This tutorial gives you a simple walkthrough of Docker Desktop, explaining every major section so you understand what’s happening behind the scenes. Inside the guide, you'll learn: • What the Docker Desktop dashboard shows • How containers appear and run • The difference between images and containers • How volumes store persistent data • How to check logs, stats, and container details • When to use Docker Desktop vs the terminal 📖 Read the full tutorial: https://lnkd.in/gEb7MXqe Once you understand the interface, the best way to learn Docker is by actually using it. You can register on Docker HOL and start learning through hands-on Docker labs built for students, beginners, and developers. ✔ Practical Docker exercises ✔ Real-world commands and workflows ✔ Step-by-step learning path 🔗 Start learning Docker: https://dockerhol.com #Docker #DockerDesktop #Containerization #DevOps #LearnDocker #DockerTutorial

🐳 Top Docker Commands Every Developer Should Know If you're working with Docker, mastering a few core commands can make your workflow faster, cleaner, and more efficient. Here are some essential Docker commands every developer should know: 🔹 1. Check Docker Version docker --version 🔹 2. Pull an Image from Docker Hub docker pull nginx 🔹 3. List Images docker images 🔹 4. Run a Container docker run -d -p 3000:3000 node-app 🔹 5. List Running Containers docker ps 🔹 6. List All Containers (including stopped) docker ps -a 🔹 7. Stop a Container docker stop <container_id> 🔹 8. Remove a Container docker rm <container_id> 🔹 9. Remove an Image docker rmi <image_id> 🔹 10. View Logs docker logs <container_id> 🔹 11. Execute Command Inside Container docker exec -it <container_id> bash 🔹 12. Build an Image docker build -t my-app . 🔹 13. Docker Compose Up docker-compose up -d 🔹 14. Docker Compose Down docker-compose down 💡 Pro Tip You don’t need to memorize everything — but knowing these commands can cover 80% of real-world Docker use cases. Mastering Docker CLI is a big step toward becoming a DevOps-ready developer 🚀 #Docker #DevOps #Containerization #WebDevelopment #CloudComputing #CICD #SoftwareEngineering #BackendDevelopment #TechSkills #Programming