𝐃𝐞𝐩𝐥𝐨𝐲𝐢𝐧𝐠 𝐅𝐥𝐚𝐬𝐤 𝐚𝐩𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐨𝐧 𝐰𝐢𝐭𝐡 𝐇𝐞𝐥𝐦 𝐨𝐧 𝐊𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬 𝐏𝐫𝐞𝐫𝐞𝐪𝐮𝐢𝐬𝐢𝐭𝐞𝐬: - Basic understanding of Kubernetes concepts (Pods, Services, Deployments). - Installed Kubernetes cluster (e.g., Minikube, GKE, EKS). - Helm installed and configured. 𝐒𝐭𝐞𝐩 1: 𝐒𝐞𝐭𝐭𝐢𝐧𝐠 𝐮𝐩 𝐲𝐨𝐮𝐫 𝐅𝐥𝐚𝐬𝐤 𝐀𝐩𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐨𝐧 ⚫ Create a simple Flask application. ⚫ Dockerize the Flask application. ⚫ Push the Docker image to a registry (optional). 𝐒𝐭𝐞𝐩 2: 𝐂𝐫𝐞𝐚𝐭𝐢𝐧𝐠 𝐚 𝐇𝐞𝐥𝐦 𝐂𝐡𝐚𝐫𝐭 ⚫Generate a Helm chart for your Flask application using helm create. ⚫Understand the structure of a Helm chart (charts/, templates/, values.yaml, etc.). ⚫Customize the Helm chart for your Flask application: - Configure Deployment settings (deployment.yaml). - Define Service specifications (service.yaml). - Set up any necessary ConfigMaps or Secrets. 𝐒𝐭𝐞𝐩 3: 𝐂𝐨𝐧𝐟𝐢𝐠𝐮𝐫𝐢𝐧𝐠 𝐕𝐚𝐥𝐮𝐞𝐬 ⚫Modify values.yaml to set environment variables, ports, and other configurations specific to your application. 𝐒𝐭𝐞𝐩 4: 𝐏𝐚𝐜𝐤𝐚𝐠𝐢𝐧𝐠 𝐚𝐧𝐝 𝐈𝐧𝐬𝐭𝐚𝐥𝐥𝐢𝐧𝐠 𝐭𝐡𝐞 𝐇𝐞𝐥𝐦 𝐂𝐡𝐚𝐫𝐭 ⚫ Package the Helm chart using helm package. ⚫Install the Helm chart onto your Kubernetes cluster using helm install. 𝐒𝐭𝐞𝐩 5: 𝐕𝐞𝐫𝐢𝐟𝐲𝐢𝐧𝐠 𝐃𝐞𝐩𝐥𝐨𝐲𝐦𝐞𝐧𝐭 ⚫Check the status of your deployment using kubectl get pods, kubectl get services. ⚫Test connectivity to your Flask application. 𝐒𝐭𝐞𝐩 6: 𝐒𝐜𝐚𝐥𝐢𝐧𝐠 𝐚𝐧𝐝 𝐔𝐩𝐠𝐫𝐚𝐝𝐢𝐧𝐠 ⚫Scale your application using Helm (helm upgrade --replicas). ⚫Upgrade your application version with Helm (helm upgrade). #FlaskOnKubernetes #HelmCharts #DevOps #KubernetesDeployment #Containerization #CloudNative #Microservices #HelmDeployments #DevOpsEngineering #K8s
Bindheyashrita Pradhan’s Post
More Relevant Posts
-
🚀 Deploy Your Flask Application with Docker! 🚀 Hi everyone! 👋 I’m excited to share how you can deploy your Flask application using Docker. Docker offers an incredible way to ensure consistent environments, simplify deployments, and enhance scalability. 🌐 Why Use Docker for Your Flask Application? Consistency: Docker containers provide a consistent environment for your application, regardless of where it's deployed. 🔄 Isolation: Each container runs in its own isolated environment, preventing conflicts with other applications. 🔒 Scalability: Easily scale your application across different environments and manage dependencies effectively. 🚀 🌐 Key Components: Dockerfile: Defines the environment for your Flask application, specifying how to build the Docker image. 📄 Docker Image: A snapshot of your application along with its dependencies, built from the Dockerfile. 🖼️ Docker Container: A running instance of a Docker image, providing an isolated environment for your application. 🐳 Docker Compose: A tool for defining and running multi-container Docker applications, simplifying the management of your application stack. 🛠️ Docker Hub: A cloud-based repository where you can store and share your Docker images. 🌐 Docker Hub: Check out the Docker image on Docker Hub: https://lnkd.in/dKnJUERy 🌐 GitHub Repository: Explore the repository, give feedback, and contribute: https://lnkd.in/d_FQt3fs Using Docker for your Flask applications not only makes your deployments more efficient but also ensures your applications are portable and scalable across different environments. Join the Docker revolution for Flask today! Feel free share your thoughts. Let's Dockerize together! 🚀 #Flask #Docker #Dockerfile #DockerImage #DockerContainer #DockerCompose #DockerHub #DevOps #Containerization
To view or add a comment, sign in
-
𝐃𝐨𝐜𝐤𝐞𝐫 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 𝐈𝐧𝐭𝐫𝐨𝐝𝐮𝐜𝐭𝐢𝐨𝐧 𝐭𝐨 𝐃𝐨𝐜𝐤𝐞𝐫: Docker is essential for modern application deployment. It's popular among developers and system administrators for its efficiency. 𝐃𝐞𝐯𝐎𝐩𝐬 𝐅𝐑𝐄𝐄 𝐖𝐞𝐛𝐢𝐧𝐚𝐫 & 𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬 https://lnkd.in/e64fYzYq 𝐃𝐨𝐜𝐤𝐞𝐫 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞: It follows a client server model. Components include Docker Client, Docker Daemon, Docker Images, Docker Containers, and Docker Registry. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐂𝐥𝐢𝐞𝐧𝐭: Interface for users to interact with Docker. Sends commands to the Docker daemon for execution. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐃𝐚𝐞𝐦𝐨𝐧: Runs on the host machine. Executes tasks requested by the Docker client, like building and running containers. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐈𝐦𝐚𝐠𝐞𝐬: Templates for containers. Contains all dependencies needed for applications. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐬: Running instances of Docker images. Contains code, runtime, libraries, environment variables, and config files. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐑𝐞𝐠𝐢𝐬𝐭𝐫𝐲: Repository for Docker images. Docker Hub is a public registry, but private registries can be created. 𝐁𝐚𝐬𝐢𝐜 𝐃𝐨𝐜𝐤𝐞𝐫 𝐂𝐨𝐦𝐦𝐚𝐧𝐝𝐬: 𝐃𝐨𝐜𝐤𝐞𝐫 𝐏𝐮𝐥𝐥: Checks if the image is locally available. Downloads from Docker Hub if not. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐁𝐮𝐢𝐥𝐝: Builds Dockerfile to create local images. Dockerfile contains build instructions. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐏𝐮𝐬𝐡: Uploads image to Docker Hub. Share images with others. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐑𝐮𝐧: Run a container from an image. Executes image's executable and exposes ports. Useful for starting various applications. Post Credit -: Omkar Srivastava #kubernetes #devops #devopsengineer #docker
To view or add a comment, sign in
-
Good morning everyone! 🚀 As a follow-up to my previous post about Docker, I would like to share my latest project, which leverages Docker Compose to create a more streamlined web application experience. This time, I've developed a comprehensive solution that enhances both the backend and frontend processes, showcasing the advantages of container orchestration. 🔍 Project Overview: This project features a Flask web application that allows users to upload images for classification using a pre-trained ResNet50 model. The standout aspect of this project is its complete containerization, utilizing Docker Compose to manage multiple containers seamlessly. With dedicated Dockerfiles for both the backend and frontend, I can ensure consistent environments across all components. 🔧 Key Learnings: - Docker Compose: Gained hands-on experience in setting up and managing a multi-container application, simplifying the orchestration of services and dependencies. - Multi-container Architecture: Learned how to structure applications to facilitate communication between the frontend and backend, improving overall performance. - Docker Networking: Explored Docker networks and how they enhance container communication, leading to a more robust deployment. 📁 This project has significantly enhanced my understanding of Docker Compose and Docker networking. By employing Docker Compose to orchestrate multiple containers, I streamlined the process of managing the application stack. Additionally, I explored how Docker networks facilitate seamless communication between the backend and frontend services, resulting in a more robust deployment. I'm eager to implement these insights in future projects! Check it out on my GitHub: https://lnkd.in/erZUgzua #Docker #DockerCompose #Containerization #Deployment #DevOps #MLOps #MachineLearning #TensorFlow #Flask #Git
To view or add a comment, sign in
-
Getting Started with Docker Basics: Images, Containers, Ports, and Volumes! 📦🚀 "Docker is revolutionizing software development and deployment, but where do you start? Let’s break it down to the basics! Here’s what you need to know about Docker: 1️⃣ Docker Images: Think of images as blueprints. They contain the code, dependencies, and configurations needed to run your application. 👉 Example: Pull an image using docker pull nginx to get a web server ready to go! 2️⃣ Docker Containers: Containers are running instances of Docker images. They are lightweight, isolated environments where your application runs. 👉 Example: Run a container with docker run nginx and watch your app come to life! 3️⃣ Port Mapping: Containers run in isolated networks, but you can map their internal ports to your local machine using -p. 👉 Example: docker run -p 8080:80 nginx maps the container’s port 80 to your machine’s port 8080. Access the app on http://localhost:8080. 4️⃣ Volume Mapping: Volumes let you persist data even when containers stop or are recreated. 👉 Example: Use -v to map local directories: docker run -v /local/data:/container/data nginx. This ensures your data remains safe. Let’s connect! If you’ve worked with Docker, share your tips or challenges below. Together, we grow! References: https://docs.docker.com/ https://lnkd.in/gG_9vXA2 #Docker #DevOps #Containerization #TechLearning #SoftwareDevelopment
To view or add a comment, sign in
-
Docker 🐬 Workflow It all starts with a developer. They write and test the application's code and define the necessary dependencies and libraries that the application needs to run. 1️⃣ Dockerfile: It is a text document that tells 🐬 how to build and run your application. It contains commands like FROM, RUN, COPY, etc., which define the application's operating environment, its dependencies, and runtime parameters. 2️⃣ Docker Image: Built from the Dockerfile, a Docker Image is a static file that is a snapshot of the application and its environment. This image is necessary to run the application on any 🐬 platform and includes all the necessary dependencies. 3️⃣ Docker Container: When Docker Images are run on a Docker Engine, they create one or more containers. Containers are isolated and self-sufficient runtime instances of the application. Since each container is created from a Docker Image, it will operate the same way in any environment using the same Docker Image. 4️⃣ Docker Hub: It is a cloud service where Docker images are stored, shared, and managed. Developers can upload their own images to Docker Hub, download others' images, and collaborate on these images. This workflow creates a process map that follows these steps: 👉 A developer writes the application code 👉 They prepare a Dockerfile that includes the code and instructions for running the application 👉 A Docker Image is created using the Dockerfile. This image is like a frozen state of the application, encompassing all its dependencies 👉 The created image can be run locally as a Docker Container for testing, or it can be uploaded to Docker Hub for sharing with the team or the public 👉 Other developers or production environments can pull this image from Docker Hub and run it as a container on their own systems #DockerWorkflow #DevOps #Containerization #DockerImage #Dockerfile #DockerContainers #Microservices #CloudComputing #DockerHub 🚨 Subscribe on M3 - Mindful Monday Musings: https://lnkd.in/dkjgrfBu 🚨 Subscribe on Medium: https://lnkd.in/ev5stfEU
To view or add a comment, sign in
-
🚀 Turbocharge Your Docker Workflow: Mastering Multi-Stage Builds 🚀 🔍 Ever felt your Docker images were bloated or your build times too long? You're not alone. Dive into my latest blog post on Medium where I break down the magic of multi-stage builds and show you how to streamline your Docker workflows like a pro. 🌟 What You'll Learn: Understanding Multi-Stage Builds: The basics and why they matter. Step-by-Step Implementation: How to create lean and efficient Docker images. Real-World Examples: Practical applications and tips to optimize your builds. 🌐 Read the full article here: https://lnkd.in/gWdpAGZF 🚀 Let's transform how we build, ship, and run applications. Join me on this journey to mastering Docker multi-stage builds and take your containerization skills to the next level! #Docker #DevOps #Containerization #TechBlog #SoftwareEngineering #MultiStageBuilds #DockerTips #Medium
To view or add a comment, sign in
-
This blog post describes "What is 𝗦𝗸𝗮𝗳𝗳𝗼𝗹𝗱 and how does it make inner development loop faster when working with 𝗞𝘂𝗯𝗲𝗿𝗻𝗲𝘁𝗲𝘀? To follow along with the blog post, you need the following: - Skaffold - Docker Desktop for Kubernetes Cluster - Draft to create Kubernetes Manifest from Docker File. #kubernetes #skaffold #draft #docker #innerdevloop
ajay mishra
mishraajay.in
To view or add a comment, sign in
-
𝐃𝐨𝐜𝐤𝐞𝐫 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 𝐃𝐞𝐯𝐎𝐩𝐬 𝐅𝐑𝐄𝐄 𝐖𝐞𝐛𝐢𝐧𝐚𝐫 & 𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬 https://lnkd.in/dmB4EgdR 𝑱𝒐𝒊𝒏 𝑶𝒖𝒓 𝑻𝒆𝒄𝒉 𝑪𝒐𝒎𝒎𝒖𝒏𝒊𝒕𝒚 -> 𝑮𝒖𝒊𝒅𝒆 𝑶𝒕𝒉𝒆𝒓’𝒔 -> 𝑾𝒊𝒏 𝑬𝒙𝒄𝒊𝒕𝒊𝒏𝒈 𝑹𝒆𝒘𝒂𝒓𝒅𝒔 ->https://app.thealpha.dev/ 𝐈𝐧𝐭𝐫𝐨𝐝𝐮𝐜𝐭𝐢𝐨𝐧 𝐭𝐨 𝐃𝐨𝐜𝐤𝐞𝐫: Docker is essential for modern application deployment. It's popular among developers and system administrators for its efficiency. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞: It follows a client server model. Components include Docker Client, Docker Daemon, Docker Images, Docker Containers, and Docker Registry. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐂𝐥𝐢𝐞𝐧𝐭: Interface for users to interact with Docker. Sends commands to the Docker daemon for execution. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐃𝐚𝐞𝐦𝐨𝐧: Runs on the host machine. Executes tasks requested by the Docker client, like building and running containers. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐈𝐦𝐚𝐠𝐞𝐬: Templates for containers. Contains all dependencies needed for applications. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐬: Running instances of Docker images. Contains code, runtime, libraries, environment variables, and config files. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐑𝐞𝐠𝐢𝐬𝐭𝐫𝐲: Repository for Docker images. Docker Hub is a public registry, but private registries can be created. 𝐁𝐚𝐬𝐢𝐜 𝐃𝐨𝐜𝐤𝐞𝐫 𝐂𝐨𝐦𝐦𝐚𝐧𝐝𝐬: 𝐃𝐨𝐜𝐤𝐞𝐫 𝐏𝐮𝐥𝐥: Checks if the image is locally available. Downloads from Docker Hub if not. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐁𝐮𝐢𝐥𝐝: Builds Dockerfile to create local images. Dockerfile contains build instructions. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐏𝐮𝐬𝐡: Uploads image to Docker Hub. Share images with others. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐑𝐮𝐧: Run a container from an image. Executes image's executable and exposes ports. Useful for starting various applications. Credit: Omkar Srivastava 𝐃𝐞𝐯𝐎𝐩𝐬 𝐅𝐑𝐄𝐄 𝐖𝐞𝐛𝐢𝐧𝐚𝐫 & 𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬 https://lnkd.in/dmB4EgdR 𝑱𝒐𝒊𝒏 𝑶𝒖𝒓 𝑻𝒆𝒄𝒉 𝑪𝒐𝒎𝒎𝒖𝒏𝒊𝒕𝒚 -> 𝑮𝒖𝒊𝒅𝒆 𝑶𝒕𝒉𝒆𝒓’𝒔 -> 𝑾𝒊𝒏 𝑬𝒙𝒄𝒊𝒕𝒊𝒏𝒈 𝑹𝒆𝒘𝒂𝒓𝒅𝒔 ->https://app.thealpha.dev/ #kubernetes #devops #devopsengineer #docker
To view or add a comment, sign in
-
𝐃𝐨𝐜𝐤𝐞𝐫 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 𝐃𝐞𝐯𝐎𝐩𝐬 𝐅𝐑𝐄𝐄 𝐖𝐞𝐛𝐢𝐧𝐚𝐫 & 𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬 https://lnkd.in/dmB4EgdR 𝑱𝒐𝒊𝒏 𝑶𝒖𝒓 𝑻𝒆𝒄𝒉 𝑪𝒐𝒎𝒎𝒖𝒏𝒊𝒕𝒚 -> 𝑮𝒖𝒊𝒅𝒆 𝑶𝒕𝒉𝒆𝒓’𝒔 -> 𝑾𝒊𝒏 𝑬𝒙𝒄𝒊𝒕𝒊𝒏𝒈 𝑹𝒆𝒘𝒂𝒓𝒅𝒔 ->https://app.thealpha.dev/ 𝐈𝐧𝐭𝐫𝐨𝐝𝐮𝐜𝐭𝐢𝐨𝐧 𝐭𝐨 𝐃𝐨𝐜𝐤𝐞𝐫: Docker is essential for modern application deployment. It's popular among developers and system administrators for its efficiency. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞: It follows a client server model. Components include Docker Client, Docker Daemon, Docker Images, Docker Containers, and Docker Registry. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐂𝐥𝐢𝐞𝐧𝐭: Interface for users to interact with Docker. Sends commands to the Docker daemon for execution. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐃𝐚𝐞𝐦𝐨𝐧: Runs on the host machine. Executes tasks requested by the Docker client, like building and running containers. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐈𝐦𝐚𝐠𝐞𝐬: Templates for containers. Contains all dependencies needed for applications. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐬: Running instances of Docker images. Contains code, runtime, libraries, environment variables, and config files. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐑𝐞𝐠𝐢𝐬𝐭𝐫𝐲: Repository for Docker images. Docker Hub is a public registry, but private registries can be created. 𝐁𝐚𝐬𝐢𝐜 𝐃𝐨𝐜𝐤𝐞𝐫 𝐂𝐨𝐦𝐦𝐚𝐧𝐝𝐬: 𝐃𝐨𝐜𝐤𝐞𝐫 𝐏𝐮𝐥𝐥: Checks if the image is locally available. Downloads from Docker Hub if not. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐁𝐮𝐢𝐥𝐝: Builds Dockerfile to create local images. Dockerfile contains build instructions. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐏𝐮𝐬𝐡: Uploads image to Docker Hub. Share images with others. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐑𝐮𝐧: Run a container from an image. Executes image's executable and exposes ports. Useful for starting various applications. Credit: Omkar Srivastava 𝐃𝐞𝐯𝐎𝐩𝐬 𝐅𝐑𝐄𝐄 𝐖𝐞𝐛𝐢𝐧𝐚𝐫 & 𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬 https://lnkd.in/dmB4EgdR 𝑱𝒐𝒊𝒏 𝑶𝒖𝒓 𝑻𝒆𝒄𝒉 𝑪𝒐𝒎𝒎𝒖𝒏𝒊𝒕𝒚 -> 𝑮𝒖𝒊𝒅𝒆 𝑶𝒕𝒉𝒆𝒓’𝒔 -> 𝑾𝒊𝒏 𝑬𝒙𝒄𝒊𝒕𝒊𝒏𝒈 𝑹𝒆𝒘𝒂𝒓𝒅𝒔 ->https://app.thealpha.dev/ #kubernetes #devops #devopsengineer #docker
To view or add a comment, sign in
-
𝐃𝐨𝐜𝐤𝐞𝐫 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 𝐈𝐧𝐭𝐫𝐨𝐝𝐮𝐜𝐭𝐢𝐨𝐧 𝐭𝐨 𝐃𝐨𝐜𝐤𝐞𝐫: Docker is essential for modern application deployment. It's popular among developers and system administrators for its efficiency. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞: It follows a client server model. Components include Docker Client, Docker Daemon, Docker Images, Docker Containers, and Docker Registry. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐂𝐥𝐢𝐞𝐧𝐭: Interface for users to interact with Docker. Sends commands to the Docker daemon for execution. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐃𝐚𝐞𝐦𝐨𝐧: Runs on the host machine. Executes tasks requested by the Docker client, like building and running containers. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐈𝐦𝐚𝐠𝐞𝐬: Templates for containers. Contains all dependencies needed for applications. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐬: Running instances of Docker images. Contains code, runtime, libraries, environment variables, and config files. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐑𝐞𝐠𝐢𝐬𝐭𝐫𝐲: Repository for Docker images. Docker Hub is a public registry, but private registries can be created. 𝐁𝐚𝐬𝐢𝐜 𝐃𝐨𝐜𝐤𝐞𝐫 𝐂𝐨𝐦𝐦𝐚𝐧𝐝𝐬: 𝐃𝐨𝐜𝐤𝐞𝐫 𝐏𝐮𝐥𝐥: Checks if the image is locally available. Downloads from Docker Hub if not. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐁𝐮𝐢𝐥𝐝: Builds Dockerfile to create local images. Dockerfile contains build instructions. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐏𝐮𝐬𝐡: Uploads image to Docker Hub. Share images with others. 𝐃𝐨𝐜𝐤𝐞𝐫 𝐑𝐮𝐧: Run a container from an image. Executes image's executable and exposes ports. Useful for starting various applications. Credit -: TheAlpha.Dev hashtag #kubernetes hashtag #devops hashtag #devopsengineer hashtag #docker
To view or add a comment, sign in
More from this author
-
Why would a company choose AWS instead of setting up and managing its own servers (With real scenario)
Bindheyashrita Pradhan 3mo -
Advanced DevOps CI/CD Automation Pipeline with Monitoring (Git, Jenkins, Docker, SonarQube, Kubernetes, Prometheus, and Grafana)
Bindheyashrita Pradhan 6mo -
Navigating AWS Load Balancers: Differences Between ALB and NLB
Bindheyashrita Pradhan 7mo