Home Operation and Maintenance Docker What is the difference between docker save and docker export?

What is the difference between docker save and docker export?

Jun 17, 2020 pm 05:44 PM

What is the difference between docker save and docker export?

First, let’s explain docker save and docker export respectively:

docker save

docker’s command line interface The design is very elegant, and the help for many commands can be viewed directly by adding --help at the end.

The help of docker save is as follows:

>docker save --help
Usage:  docker save [OPTIONS] IMAGE [IMAGE...]
Save one or more images to a tar archive (streamed to STDOUT by default)
Options:
      --help            Print usage
  -o, --output string   Write to a file, instead of STDOUT
Copy after login

As can be seen from the command line help, docker save is a tool used to package and save one or more images.

For example, if we want to package postgres and mongo in the mirror library, we can execute:

docker save -o images.tar postgres:9.6 mongo:3.4
Copy after login

The packaged images.tar contains the two images of postgres:9.6 and mongo:3.4.

Although the command line parameters require the image to be specified, the container can actually be packaged, for example:

>docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS               NAMES
3623943d369f        postgres:9.6        "docker-entrypoint..."   3 hours ago         Up 3 hours          5432/tcp            postgres
>docker save -o b.tar postgres
>docker save -o c.tar postgres:9.6
>ls -al
-rwxrwxrwx 1 root root 277886464 8月  26 14:40 b.tar
-rwxrwxrwx 1 root root 277886464 8月  26 14:41 c.tar
Copy after login

As you can see from the above command, b.tar and c.tar are exactly the same . This shows that if docker save specifies a container, docker save will save the image behind the container.

Load the packaged image using docker load, for example:

docker load -i images.tar
Copy after login

The above command will load postgres:9.6 and mongo:3.4. If the local image library These two images already exist and will be overwritten.

The application scenario of docker save is if your application is a combination of multiple images arranged using docker-compose.yml, but the client server you want to deploy cannot connect to the external network. At this time, you can use docker save to package the used image, and then copy it to the client server and use docker load to load it.

docker export

As usual, check the help of docker export:

>docker export --help
Usage:  docker export [OPTIONS] CONTAINER
Export a container's filesystem as a tar archive
Options:
      --help            Print usage
  -o, --output string   Write to a file, instead of STDOUT
Copy after login

As can be seen from the help, docker export is used to convert container files The system is packaged. For example:

docker export -o postgres-export.tar postgres
Copy after login

docker export needs to specify the container, and cannot specify image or container like docker save.

Load the packaged container using docker import, for example:

docker import postgres-export.tar postgres:latest
Copy after login

As can be seen from the above command, docker import will become an image after importing the container, not Restore to a container.

Another point is that docker import can specify IMAGE[:TAG], which means we can specify a new name for the image. If an image with the same name already exists in the local image library, the name of the original image will be stripped and assigned to the new image. The original image will become a ghost and can only be operated through IMAGE ID.

The application scenario of docker export is mainly used to make a basic image. For example, you start a container from an ubuntu image, then install some software and make some settings, and then use docker export to save it as a basic image. Then, distribute this image to others for use, such as as a basic development environment.

The difference between docker save and docker export

  • docker save saves the image (image), and docker export saves the container (container) ;

  • docker load is used to load the image package, and docker import is used to load the container package, but both will be restored to the image;

  • docker load cannot rename the loaded image, but docker import can specify a new name for the image.

Recommended tutorial: docker

The above is the detailed content of What is the difference between docker save and docker export?. For more information, please follow other related articles on the PHP Chinese website!

Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Tools

Notepad++7.3.1

Notepad++7.3.1

Easy-to-use and free code editor

SublimeText3 Chinese version

SublimeText3 Chinese version

Chinese version, very easy to use

Zend Studio 13.0.1

Zend Studio 13.0.1

Powerful PHP integrated development environment

Dreamweaver CS6

Dreamweaver CS6

Visual web development tools

SublimeText3 Mac version

SublimeText3 Mac version

God-level code editing software (SublimeText3)

Docker Interview Questions: Ace Your DevOps Engineering Interview Docker Interview Questions: Ace Your DevOps Engineering Interview Apr 06, 2025 am 12:01 AM

Docker is a must-have skill for DevOps engineers. 1.Docker is an open source containerized platform that achieves isolation and portability by packaging applications and their dependencies into containers. 2. Docker works with namespaces, control groups and federated file systems. 3. Basic usage includes creating, running and managing containers. 4. Advanced usage includes using DockerCompose to manage multi-container applications. 5. Common errors include container failure, port mapping problems, and data persistence problems. Debugging skills include viewing logs, entering containers, and viewing detailed information. 6. Performance optimization and best practices include image optimization, resource constraints, network optimization and best practices for using Dockerfile.

Docker Volumes: Managing Persistent Data in Containers Docker Volumes: Managing Persistent Data in Containers Apr 04, 2025 am 12:19 AM

DockerVolumes ensures that data remains safe when containers are restarted, deleted, or migrated. 1. Create Volume: dockervolumecreatemydata. 2. Run the container and mount Volume: dockerrun-it-vmydata:/app/dataubuntubash. 3. Advanced usage includes data sharing and backup.

Docker Security Hardening: Protecting Your Containers From Vulnerabilities Docker Security Hardening: Protecting Your Containers From Vulnerabilities Apr 05, 2025 am 12:08 AM

Docker security enhancement methods include: 1. Use the --cap-drop parameter to limit Linux capabilities, 2. Create read-only containers, 3. Set SELinux tags. These strategies protect containers by reducing vulnerability exposure and limiting attacker capabilities.

Using Docker with Linux: A Comprehensive Guide Using Docker with Linux: A Comprehensive Guide Apr 12, 2025 am 12:07 AM

Using Docker on Linux can improve development and deployment efficiency. 1. Install Docker: Use scripts to install Docker on Ubuntu. 2. Verify the installation: Run sudodockerrunhello-world. 3. Basic usage: Create an Nginx container dockerrun-namemy-nginx-p8080:80-dnginx. 4. Advanced usage: Create a custom image, build and run using Dockerfile. 5. Optimization and Best Practices: Follow best practices for writing Dockerfiles using multi-stage builds and DockerCompose.

Advanced Docker Networking: Mastering Bridge, Host & Overlay Networks Advanced Docker Networking: Mastering Bridge, Host & Overlay Networks Apr 03, 2025 am 12:06 AM

Docker provides three main network modes: bridge network, host network and overlay network. 1. The bridge network is suitable for inter-container communication on a single host and is implemented through a virtual bridge. 2. The host network is suitable for scenarios where high-performance networks are required, and the container directly uses the host's network stack. 3. Overlay network is suitable for multi-host DockerSwarm clusters, and cross-host communication is realized through the virtual network layer.

How to update the image of docker How to update the image of docker Apr 15, 2025 pm 12:03 PM

The steps to update a Docker image are as follows: Pull the latest image tag New image Delete the old image for a specific tag (optional) Restart the container (if needed)

How to create a mirror in docker How to create a mirror in docker Apr 15, 2025 am 11:27 AM

Steps to create a Docker image: Write a Dockerfile that contains the build instructions. Build the image in the terminal, using the docker build command. Tag the image and assign names and tags using the docker tag command.

How to use docker desktop How to use docker desktop Apr 15, 2025 am 11:45 AM

How to use Docker Desktop? Docker Desktop is a tool for running Docker containers on local machines. The steps to use include: 1. Install Docker Desktop; 2. Start Docker Desktop; 3. Create Docker image (using Dockerfile); 4. Build Docker image (using docker build); 5. Run Docker container (using docker run).

See all articles