Loading...
No results found.

Apply your skills in Google Cloud console

Lab setup instructions and requirements
Protect your account and progress. Always use a private browser window and lab credentials to run this lab.

Deploy a Static Site Using Traefik and Cloud Run

Lab 30 minutes universal_currency_alt 1 Credit show_chart Introductory
info This lab may incorporate AI tools to support your learning.
This content is not yet optimized for mobile devices.
For the best experience, please visit us on a desktop computer using a link sent by email.

gem-cloud-run-traefik-website

Google Cloud self-paced labs logo

Activate Cloud Shell

Cloud Shell is a virtual machine that is loaded with development tools. It offers a persistent 5GB home directory and runs on the Google Cloud. Cloud Shell provides command-line access to your Google Cloud resources.

  1. Click Activate Cloud Shell Activate Cloud Shell icon at the top of the Google Cloud console.

When you are connected, you are already authenticated, and the project is set to your PROJECT_ID. The output contains a line that declares the PROJECT_ID for this session:

Your Cloud Platform project in this session is set to YOUR_PROJECT_ID

gcloud is the command-line tool for Google Cloud. It comes pre-installed on Cloud Shell and supports tab-completion.

  1. (Optional) You can list the active account name with this command:
gcloud auth list

  1. Click Authorize.

  2. Your output should now look like this:

Output:

ACTIVE: * ACCOUNT: student-01-xxxxxxxxxxxx@qwiklabs.net To set the active account, run: $ gcloud config set account `ACCOUNT`
  1. (Optional) You can list the project ID with this command:
gcloud config list project

Output:

[core] project = <project_ID>

Example output:

[core] project = qwiklabs-gcp-44776a13dea667a6 Note: For full documentation of gcloud, in Google Cloud, refer to the gcloud CLI overview guide.

Overview

In this lab, you'll learn how to deploy a static website using Traefik as a reverse proxy and Cloud Run for serving the content. You will containerize a simple static site, push the image to Artifact Registry, configure Traefik to route traffic, and deploy it all to Cloud Run.

Task 1. Set Up Your Environment

Configure your Google Cloud environment for this lab.

  1. Enable the necessary APIs: Cloud Run, Artifact Registry, and Cloud Build.
gcloud services enable run.googleapis.com artifactregistry.googleapis.com cloudbuild.googleapis.com Note:
This command enables the required Google Cloud services.
  1. Set your Project ID.
gcloud config set project {{{ project_0.project_id | "PROJECT_ID" }}} Note:
Replace PROJECT_ID with your actual project ID.
  1. Set your default run region.
gcloud config set run/region {{{ project_0.default_region | "REGION" }}} Note:
Replace REGION with your desired region (e.g., us-central1).

Task 2. Create an Artifact Registry Repository

Create a Docker repository in Artifact Registry to store your container images.

  1. Create a Docker repository named 'traefik-site'.
gcloud artifacts repositories create traefik-repo --repository-format=docker --location={{{ project_0.default_region | "REGION" }}} --description="Docker repository for static site images" Note:
This command creates a Docker repository in Artifact Registry.

Task 3. Build and Push the Static Site Image

Create a simple static site, containerize it using Docker, and push the image to Artifact Registry.

  1. Create a directory for your static site.
mkdir traefik-site && cd traefik-site && mkdir public
  1. Create an public/index.html file with some simple content.
cat > public/index.html <<EOF <html> <head> <title>My Static Website</title> </head> <body> <p>Hello from my static website on Cloud Run!</p> </body> </html> EOF Note:
This is the HTML content for the static site.
  1. Authenticate Docker to Artifact Registry.
gcloud auth configure-docker {{{ project_0.default_region | "REGION" }}}-docker.pkg.dev Note:
This command configures Docker to use your Google Cloud credentials.
  1. Create a traefik.yml with the following content:
entryPoints: web: address: ":8080" providers: file: filename: /etc/traefik/dynamic.yml watch: true log: level: INFO Note:
This command creates the Traefik configuration file.
  1. Create a dynamic.yml with the following content:
http: routers: static-files: rule: "PathPrefix(`/`)" entryPoints: - web service: static-service services: static-service: loadBalancer: servers: - url: "http://localhost:8000" Note:
This command creates the dynamic content configuration file.

Task 4. Create the Dockerfile

Define the Docker image for Traefik and your static website.

  1. Create a Dockerfile with the following content:
FROM alpine:3.20 # Install traefik and caddy RUN apk add --no-cache traefik caddy # Copy configs and static files COPY traefik.yml /etc/traefik/traefik.yml COPY dynamic.yml /etc/traefik/dynamic.yml COPY public/ /public/ # Cloud Run uses port 8080 EXPOSE 8080 # Run static server (on 8000) and Traefik (on 8080) ENTRYPOINT [ "caddy" ] CMD [ "file-server", "--listen", ":8000", "--root", "/public", "&", "traefik" ] Note:
This Dockerfile uses the official Alpine image, sets the working directory, and copies your website and Caddyfile. Traefik will be used to handle routing and Caddy used to serve web content.

Task 5. Build and push the Docker image

Build the Docker image and push it to Artifact Registry.

  1. Build the Docker image. Replace and with your region and project ID.
docker build -t {{{ project_0.default_region | "REGION" }}}-docker.pkg.dev/{{{ project_0.project_id | "PROJECT_ID" }}}/traefik-repo/traefik-static-site:latest . Note:
This command builds the Docker image and tags it with the Artifact Registry repository URL.
  1. Push the Docker image to Artifact Registry.
docker push {{{ project_0.default_region | "REGION" }}}-docker.pkg.dev/{{{ project_0.project_id | "PROJECT_ID" }}}/traefik-repo/traefik-static-site:latest Note:
This command pushes the Docker image to Artifact Registry.

Task 6. Deploy to Cloud Run

Deploy the container image to Cloud Run.

  1. Deploy the service to Cloud Run. Replace and with your region and project ID.
gcloud run deploy traefik-static-site --image {{{ project_0.default_region | "REGION" }}}-docker.pkg.dev/{{{ project_0.project_id | "PROJECT_ID" }}}/traefik-repo/traefik-static-site:latest --platform managed --allow-unauthenticated --port 8000 Note:
This command deploys the Docker image to Cloud Run and allows unauthenticated access.
  1. When prompted, confirm the service name as traefik-static-site and allow unauthenticated invocations.
Note:
This configures the service name and permissions.
  1. Note the service URL provided by Cloud Run.
Note:
This is the URL where your static website is accessible.

Task 7. Access your website

Access the deployed website through the Cloud Run service URL.

  1. Open the Cloud Run service URL in your web browser.
Note:
Verify that your static website is displayed correctly.

Congratulations!

Congratulations! You have successfully deployed a static website using Traefik and Cloud Run. You learned how to containerize a static site, store the image in Artifact Registry, configure Traefik as a reverse proxy, and deploy it all to Cloud Run.

Additional Resources

Manual Last Updated Jun 25, 2025

Lab Last Tested Jun 25, 2025

Before you begin

  1. Labs create a Google Cloud project and resources for a fixed time
  2. Labs have a time limit and no pause feature. If you end the lab, you'll have to restart from the beginning.
  3. On the top left of your screen, click Start lab to begin

Use private browsing

  1. Copy the provided Username and Password for the lab
  2. Click Open console in private mode

Sign in to the Console

  1. Sign in using your lab credentials. Using other credentials might cause errors or incur charges.
  2. Accept the terms, and skip the recovery resource page
  3. Don't click End lab unless you've finished the lab or want to restart it, as it will clear your work and remove the project

This content is not currently available

We will notify you via email when it becomes available

Great!

We will contact you via email if it becomes available

One lab at a time

Confirm to end all existing labs and start this one

Use private browsing to run the lab

Using an Incognito or private browser window is the best way to run this lab. This prevents any conflicts between your personal account and the Student account, which may cause extra charges incurred to your personal account.