Virtualization

From container image to running service

Trace an image from build and registry to a running container, then follow a published port and persistent volume.

One host · replaceable container · separate volumeBuild contextBuild contextPush imagePush imagePull imagePull imageStart instanceStart instanceapp-user ↔ published-portPort mappingPort mappingMounted dataMounted dataApplication sourceApplication sourceImage buildImage buildImage registryImage registryHost OS and runtimeHost OS and runtimeRunning containerRunning containerPublished portPublished portLocal clientLocal clientPersistent volumePersistent volume
Legend

Current step

Build a reusable image

A Dockerfile and selected build context produce versioned, read-only image layers.

An image is a reusable template; a container is a running process environment. Published ports expose only the configured path, and a volume keeps selected data separate from a replaceable container.

Documentation example: addresses use the RFC 5737 ranges and ASNs use the reserved private range. Nothing here connects to a real network.

Tags

  • docker
  • container
  • image
  • registry
  • port mapping
  • volume
  • runtime

Lessons using this diagram