Wdrażanie na maszynie wirtualnej w chmurze

You've containerized your app with Docker. Now, it's time to put it online! This lesson covers deploying your Dockerized application to a cloud Virtual Machine (VM).

A VM acts like a remote computer where your app can run 24/7, accessible to users worldwide.

A Virtual Machine (VM) is a software-based computer that runs on a physical server in a cloud data center. It has its own CPU, memory, storage, and network interface, just like a physical machine.

• Isolation: Each VM is isolated from others.
• Flexibility: You choose the operating system (OS) and resources.
• Persistence: Your app keeps running even if you disconnect.

Major cloud providers offer VMs:

• AWS EC2: Amazon Elastic Compute Cloud
• GCP Compute Engine: Google Cloud Platform
• Azure Virtual Machines: Microsoft Azure

For your Dockerized app, a Linux OS (like Ubuntu or CentOS) is typically the best and most cost-effective choice.

Launching a VM involves a few key steps:

1. Instance Type: Select CPU/RAM based on app needs.
2. Region: Choose a geographical location close to your users.
3. Key Pair: Create a secure SSH key for access.
4. Security Group/Firewall: Define network rules (e.g., allow SSH, HTTP/S).

These are configured through your cloud provider's console or API.

Once your VM is launched, you'll connect to it using SSH (Secure Shell). This encrypted protocol allows you to execute commands remotely and securely.

You'll use the private key from your key pair to authenticate.

Your cloud VM starts fresh. The first step is to install Docker Engine, which allows your VM to run Docker containers.

For Ubuntu, you'd update packages, then install Docker. This makes your VM a Docker host!

With Docker installed, you need your application's Docker image on the VM. If you pushed your image to a registry like Docker Hub or a private cloud registry, you can simply pull it.

Replace your-username/your-app:latest with your actual image name.

Now, run your container! The -p flag maps a port on your VM (e.g., 80) to a port inside your container (e.g., 3000, where your app listens).

The -d flag runs it in 'detached' mode, so it runs in the background.

Even if your container is running, users can't reach it unless you open the necessary ports on your VM's firewall (often called 'security groups' in cloud providers).

You'll need to allow inbound traffic on port 80 (for HTTP) and potentially 443 (for HTTPS) from anywhere (0.0.0.0/0).

After running your container and configuring the firewall, you can verify your deployment.

• SSH: Use docker ps to see running containers.
• Browser: Navigate to your VM's public IP address or domain name in a web browser.

If you see your app, congratulations!

You've deployed your Dockerized app to a cloud VM. What's the primary tool used to securely connect and manage your remote VM?

In this lesson, you learned how to deploy your Dockerized application to a cloud Virtual Machine. We covered selecting a provider, launching an instance, connecting via SSH, installing Docker, pulling and running your image, and configuring network access.

This is a foundational step for making your SaaS application publicly available!