instruction: Create a Dockerfile for workloads
output: ```dockerfile
  from there. See the guide Create static Pods
  for more information.Note:The spec of a static Pod cannot refer to other API objects
  (e.g., ServiceAccount,
  ConfigMap,
  Secret, etc).Pods with multiple containersPods are designed to support multiple cooperating processes (as containers) that form
  a cohesive unit of service. The containers in a Pod are automatically co-located and
  co-scheduled on the same physical or virtual machine in the cluster. The containers
  can share resources and dependencies, communicate with one another, and coordinate
  when and how they are terminated.Pods in a Kubernetes cluster are used in two main ways:Pods that run a single container. The "one-container-per-Pod" model is the
  most common Kubernetes use case; in this case, you can think of a Pod as a
  wrapper around a single container; Kubernetes manages Pods rather than managing
  the containers directly.Pods that run multiple containers that need to work together. A Pod can
  encapsulate an application composed of
  multiple co-located containers that are
  tightly coupled and need to share resources. These co-located containers
  form a single cohesive unit of service—for example, one container serving data
  stored in a shared volume to the public, while a separate
  sidecar container
  refreshes or updates those files.
  The Pod wraps these containers, storage resources, and an ephemeral network
  identity together as a single unit.For example, you might have a container that
  acts as a web server for files in a shared volume, and a separate
  sidecar container
  that updates those files
  ```