AWS EC2 – Building Services with Docker Compose – Abandoned

#1. Service Installation

  1. Register the apt repository
# Add Docker's official GPG key:
sudo apt-get update
sudo apt-get install ca-certificates curl
sudo install -m 0755 -d /etc/apt/keyrings
sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc
sudo chmod a+r /etc/apt/keyrings/docker.asc

# Add the repository to Apt sources:
echo \
  "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu \
  $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | \
  sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
sudo apt-get update

2. Installation

sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin -y

3. Failure due to lack of resources

Deploying independent db and WordPress in pairs using docker compose resulted in four services running, leaving no remaining resources on the server.

Using t4g.small and t4g.micro both failed due to insufficient resources.

It doesn’t work just by separately deploying each resource bluntly…

I’m giving up again and going to try deploying pods with k8s…

Even a single Docker service requests 2 GB.

Giving up

포기

전체 과정 블로그 /aws-ec2-mariadb-환경-설정