AWS, Azure & GCP · Cloud across providers

How do you run containers in the cloud?

EasycontainersdockerregistriesUpdated Oct 2026
Quiz this track

Short answer

You package the app and dependencies into an image, push it to a registry, and run it on a managed container service or orchestrator. Managed options range from simple run-a-container services to full Kubernetes.

A container image bundles the application, runtime and libraries into an immutable artifact. The cloud runs that image on managed capacity, which gives you consistent behaviour from laptop to production and a clear deploy unit.

Managed options

  • Run a container without a cluster: Cloud Run, Azure Container Apps, App Runner
  • Managed orchestrators: ECS with Fargate, AKS, EKS, GKE
  • Batch or job runners for finite work
  • Registries such as ECR, ACR and Artifact Registry for images and scanning
dockerfile
FROM node:20-alpine
WORKDIR /app
COPY package*.json ./
RUN npm ci --omit=dev
COPY . .
USER node
CMD ["node", "server.js"]
A small multi-stage-style image that runs as a non-root user.

The operational work shifts to image hygiene, vulnerability scanning, registry permissions, resource limits and rollout strategy. A container does not automatically make an app scalable; it still needs health checks, graceful shutdown and externalised state.

Pin base image versions and rebuild regularly. A stale base image accumulates unpatched vulnerabilities even if your application code has not changed.

Follow-ups you should expect

Interviewers use these to check whether the first answer was understanding or memorisation.

  1. 1When would you use a container service instead of Kubernetes?
  2. 2Why should a container run as a non-root user?
  3. 3How do you keep base images patched?
  4. 4What does a container not solve about application state?

Say it in the interview

I package the application and its dependencies into an image, push it to a registry, and run it on a managed service. That could be a simple run-a-container platform or a full orchestrator like EKS or GKE. The container gives me a consistent deploy unit, but I still own image scanning, resource limits, health checks and graceful shutdown.

Use this as a model, not a script. Saying it in your own words is what makes it survive follow-up pressure.

Related questions

Reading is step one

Now say it out loud.

Understanding an answer and delivering it under pressure are different skills. Rehearse this topic in a live AWS, Azure & GCP mock interview and get scored feedback on depth, clarity and confidence.