•  Home
  •  Dashboard
  •  Company
    • About Us
    • Blog
    • Careers
    • Contact Us
    • Data Centers
    • Looking Glass
    • Network
    • Reseller
  •  Hosting Services
    • Infrastructure
      • iColocation
    • Compute
      • cMetal
      • cVirtual
    • Storage
      • sObject
      • sBlock
    • Networking
      • nCDN
      • nIP Transit
      • nWavelength
    • Protection
      • pBackup
      • pDDoS
  •  Solutions
    • Ecommerce
    • Finance
    • Gaming
    • Hosting
    • Management
    • Security
    • System Integrator
  •  Support
    • Community
    • Knowledge Base
    • Open A Ticket
  •  USA & Canada: 800-933-1517
  •  International: 626-549-2801
  •  Email: sales@psychz.net
  • Services
    • new-colocation-header-img
      Infrastructure
      • iColocation
    • new-compute-header-img
      Compute
      • cMetal
      • cVirtual
    • new-storage-header-img
      Storage
      • sObject
      • sBlock
    • new-networking-header-img
      Networking
      • nCDN
      • nIP Transit
      • nWavelength
    • new-protection-header-img
      Protection
      • pBackup
      • pDDoS
  • Solutions
    • Ecommerce
    • Security
    • Gaming
    • Hosting
    • Management
    • Finance
    • System Integrator
  • Dashboard

Docker container vs Image

  • Home
  • Client
  • Qa Forum
  • Docker container vs Image

Posted By: Chris | 1 Replies | Last Reply On: Oct 27, 2017 12:13:01

How is a docker container different from an image?  Which one is preferred? 

Psychz - Ramesh

Votes: 0Posted On: Oct 27, 2017 12:13:01
 

Images and Containers are often used interchangeably. However, they are not the same and functions differently.
Let me explain you both with simplest of example
 
A docker image is like an application which has an executable file on disk. They are never running.
On the other hand, When you execute an application, it creates an instance in memory that is running. This is like a Docker container.
 
Okay, let me put it in more simpler words,
 
A docker image contains an operating system along with many applications. Whereas, a container is running an instance generated from an image.
So now each time you start a container from an image, you are actually “starting over”. Which means that changes made to a container do not carry over to the base image. However, changes made within a container are saved since they are captured in that specific container’s filesystem layer.

Was this reply helpful?

Related topics

  • Smart guide to managing Docker container
  • How To Run Kubernetes on Psychz Networks Bare Metal Servers
  • Docker Container vs VM
  • SSH into Docker Container
  • OpenShift vs. Docker
  • LXD vs Docker
  • Docker remove all images
  • Docker Remove All Containers
  • How to add Image Optimization
  • Kubernetes vs Jenkins | How are they different?
  • Managing systemd services and units using systemctl commands
  • Tools That Make Kubernetes Easier
  • Red Hat: Not just about Linux anymore!
  • Scaling your Business with a Dedicated Server and Containers
  • Most Common Linux Distros
Copyright © 2025 Psychz Networks,
A Profuse Solutions Inc Company
Hosting Services
Infrastructure
  • iColocation
Compute
  • cMetal
  • cVirtual
Storage
  • sObject
  • sBlock
Networking
  • nCDN
  • nIP Transit
  • nWavelength
Protection
  • pBackup
  • pDDoS
Company
  • About Us
  • Blog
  • Careers
  • Contact Us
  • Data Centers
  • Looking Glass
  • Network
  • Reseller
Policies
  • Acceptable Usage Policy
  • Privacy Policy
  • Service Level Agreement
  • Terms and Conditions
Support
  • Community
  • Knowledge Base
  • Open A Ticket
Get In Touch
  • Psychz Networks,
    A Profuse Solutions Company
    611 Wilshire Blvd #300
    Los Angeles,California 90017
    USA
  • US/Canada: 800-933-1517
  • International: 626-549-2801