ChatGPT解决这个技术问题 Extra ChatGPT

How to copy Docker images from one host to another without using a repository

How do I transfer a Docker image from one machine to another one without using a repository, no matter private or public?

I create my own image in VirtualBox, and when it is finished I try to deploy to other machines to have real usage.

Since it is based on my own based image (like Red Hat Linux), it cannot be recreated from a Dockerfile. My dockerfile isn't easily portable.

Are there simple commands I can use? Or another solution?


G
Gautam Krishna R

You will need to save the Docker image as a tar file:

docker save -o <path for generated tar file> <image name>

Then copy your image to a new system with regular file transfer tools such as cp, scp or rsync(preferred for big files). After that you will have to load the image into Docker:

docker load -i <path to image tar file>

PS: You may need to sudo all commands.

EDIT: You should add filename (not just directory) with -o, for example:

docker save -o c:/myfile.tar centos:16

This is the better answer for images.
also, it is better to use repo:tag as the image reference rather than image id. If you use image id, the loaded image will not retain the tag (and you will have to do another step to tag the image).
I used the image id instead of the name:tag Now I'm sitting here, loaded the image and have a for REPOSITORY and TAG. What is the right way to bring the name and tag back? @wisbucky
To tag, first identity the IMAGE ID using docker images, then use docker tag DESIREDIMAGEID mycompany/myreponame. If your image id is 591de551d6e4, you can abbreviate the image id: docker tag 59 mycompany/myreponame
@serge not at all, it even has an example where a windows path is used...
k
kolypto

Transferring a Docker image via SSH, bzipping the content on the fly:

docker save <image> | bzip2 | ssh user@host docker load

Note that docker load automatically decompresses images for you. It supports gzip, bzip2 and xz.

It's also a good idea to put pv in the middle of the pipe to see how the transfer is going:

docker save <image> | bzip2 | pv | ssh user@host docker load

(More info about pv: home page, man page).

Important note from @Thomas Steinbach: on high bandwidth, bzip won't be able to compress fast enough. In case you can upload at 10 MB/s and more, gzip/gunzip will be much faster than bzip2.

If you're on 3G and your Internet is slow, @jgmjgm suggests that you can use xz: it offers a higher compression ratio.


When using docker-machine, you can do docker $(docker-machine config mach1) save <image> | docker $(docker-machine config mach2) load to copy images between machines mach1 and mach2.
@manojlds eval $(docker-machine env dev) is good for general communication with a single docker host but not to copy between two machines, since this involves two different docker hosts / docker machines.
to do this in reverse (remote to local): ssh target_server 'docker save image:latest | bzip2' | pv | bunzip2 | docker load
Is there any way to do this when docker requires sudo on the target machine? I tried (without compression) docker save my_img:v1 | ssh -t -t my_user@my_machine sudo docker load. Without the "-t" switch, sudo complains sudo: sorry, you must have a tty to run sudo; with one "-t" it's the same message because ssh says Pseudo-terminal will not be allocated because stdin is not a terminal. and finally, with two "-t"s, I get the content of the tar file (i.e. the image) on my terminal. Any ideas?
@JosefStark I needed to add "Defaults: !requiretty" when editing the sudoers file to stop the "Sorry" message from sudo. I don't know how much of a difference it makes but I also put everything after the user@host in quotes (so "[...] | ssh user@host 'bunzip2 | sudo docker load'").
M
Martti Laine

To save an image to any file path or shared NFS place see the following example.

Get the image id by doing:

docker images

Say you have an image with id "matrix-data".

Save the image with id:

docker save -o /home/matrix/matrix-data.tar matrix-data

Copy the image from the path to any host. Now import to your local Docker installation using:

docker load -i <path to copied image file>

v
vitalets

You can use a one-liner with DOCKER_HOST variable:

docker save app:1.0 | gzip | DOCKER_HOST=ssh://user@remotehost docker load

This is definitely the command I was looking for, I think this answer deserves more love
prereqs: ssh credentials setup on the remote (ssh-copy-id) and the local and remote user both need to be in the docker group (sudo usermod -aG docker $USER)
Are there any (performance) differences to ssh user@remotehost docker load here?
T
Thorbjørn Ravn Andersen

First save the Docker image to a compressed archive:

docker save <docker image name> | gzip > <docker image name>.tar.gz

Then load the exported image to Docker using the below command:

zcat <docker image name>.tar.gz | docker load

For loading, docker load < my-image.tar.gz is sufficient. The image gets decompressed automatically for gzip, bzip2, and xz.
P
Peter Mortensen

Run

docker images

to see a list of the images on the host. Let's say you have an image called awesomesauce. In your terminal, cd to the directory where you want to export the image to. Now run:

docker save awesomesauce:latest > awesomesauce.tar

Copy the tar file to a thumb drive or whatever, and then copy it to the new host computer.

Now from the new host do:

docker load < awesomesauce.tar

Now go have a coffee and read Hacker News...


Worth noting here is that this will only work if save and load are executed on the same OS. Use docker save [image] -o file.tar and docker load -i file.tar to avoid this!
docker save [image] -o file.tar also appears to be wildly faster
@AndreasForslöw Why does using pipes mean that this only works on the same OS?
v
vitaut

For a flattened export of a container's filesystem, use;

docker export CONTAINER_ID > my_container.tar

Use cat my_container.tar | docker import - to import said image.


it shall be cat my_container.tar | docker import - my_container:new if import locally according to cmd help
This is more for backing up a running container than for deploying an image.
I tried docker save at ubuntu machines which all docker images up and running good. Then i docker load them at windows machine. There are many errors when i docker run or start them. Any ideas whats wrong?
L
Louis

docker-push-ssh is a command line utility I created just for this scenario.

It sets up a temporary private Docker registry on the server, establishes an SSH tunnel from your localhost, pushes your image, then cleans up after itself.

The benefit of this approach over docker save (at the time of writing most answers are using this method) is that only the new layers are pushed to the server, resulting in a MUCH quicker upload.

Oftentimes using an intermediate registry like dockerhub is undesirable, and cumbersome.

https://github.com/brthor/docker-push-ssh

Install:

pip install docker-push-ssh

Example:

docker-push-ssh -i ~/my_ssh_key username@myserver.com my-docker-image

The biggest caveat is that you have to manually add your localhost to Docker's insecure_registries configuration. Run the tool once and it will give you an informative error:

Error Pushing Image: Ensure localhost:5000 is added to your insecure registries.
More Details (OS X): https://stackoverflow.com/questions/32808215/where-to-set-the-insecure-registry-flag-on-mac-os

Where should I set the '--insecure-registry' flag on Mac OS?


This is a promising utility. Do any other answers offer a solution which copies only the updated layers? But, I had to work through a) no py3 support, b) ssh identify file must be specified though mine is in default location, and c) port 5000 is already in use on my servers and there is no option to change to another port.
@nmgeek Consider making a PR to the utility on GitHub so others can benefit from your changes.
There is PR for Python3: github.com/brthor/docker-push-ssh/pull/15 @brthornbury can you merge it?
J
John Kugelman

When using docker-machine, you can copy images between machines mach1 and mach2 with:

docker $(docker-machine config <mach1>) save <image> | docker $(docker-machine config <mach2>) load

And of course you can also stick pv in the middle to get a progess indicator:

docker $(docker-machine config <mach1>) save <image> | pv | docker $(docker-machine config <mach2>) load

You may also omit one of the docker-machine config sub-shells, to use your current default docker-host.

docker save <image> | docker $(docker-machine config <mach>) load

to copy image from current docker-host to mach

or

docker $(docker-machine config <mach>) save <image> | docker load

to copy from mach to current docker-host.


P
Peter Mortensen

I assume you need to save couchdb-cartridge which has an image id of 7ebc8510bc2c:

stratos@Dev-PC:~$ docker images
REPOSITORY                             TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
couchdb-cartridge                      latest              7ebc8510bc2c        17 hours ago        1.102 GB
192.168.57.30:5042/couchdb-cartridge   latest              7ebc8510bc2c        17 hours ago        1.102 GB
ubuntu                                 14.04               53bf7a53e890        3 days ago          221.3 MB

Save the archiveName image to a tar file. I will use the /media/sf_docker_vm/ to save the image.

stratos@Dev-PC:~$ docker save imageID > /media/sf_docker_vm/archiveName.tar

Copy the archiveName.tar file to your new Docker instance using whatever method works in your environment, for example FTP, SCP, etc.

Run the docker load command on your new Docker instance and specify the location of the image tar file.

stratos@Dev-PC:~$ docker load < /media/sf_docker_vm/archiveName.tar

Finally, run the docker images command to check that the image is now available.

stratos@Dev-PC:~$ docker images
REPOSITORY                             TAG        IMAGE ID         CREATED             VIRTUAL SIZE
couchdb-cartridge                      latest     7ebc8510bc2c     17 hours ago        1.102 GB
192.168.57.30:5042/couchdb-cartridge   latest     bc8510bc2c       17 hours ago        1.102 GB
ubuntu                                 14.04      4d2eab1c0b9a     3 days ago          221.3 MB

Please find this detailed post.


P
Peter Mortensen

To transfer images from your local Docker installation to a minikube VM:

docker save <image> | (eval $(minikube docker-env) && docker load)

q
quine9997

REAL WORLD EXAMPLE

#host1
systemctl stop docker
systemctl start docker
docker commit -p 1d09068ef111 ubuntu001_bkp3
#create backup
docker save -o ubuntu001_bkp3.tar ubuntu001_bkp3

#upload ubuntu001_bkp3.tar to my online drive
aws s3 cp ubuntu001_bkp3.tar s3://mybucket001/


#host2
systemctl stop docker
systemctl start docker
cd /dir1

#download ubuntu001_bkp3.tar from my online drive
aws s3 cp s3://mybucket001/ubuntu001_bkp3.tar /dir1

#restore backup
cat ./ubuntu001_bkp3.tar  | docker load
docker run --name ubuntu001 -it ubuntu001_bkp3:latest bash
docker ps -a
docker attach ubuntu001





Why are you stopping docker service before you do anything?
it's not working for me !! Getting this error --- > 'open /var/lib/docker/tmp/docker-import-315206241/app/json: no such file or directory'
P
Peter Mortensen

All other answers are very helpful. I just went through the same problem and figure out an easy way with docker machine scp.

Since Docker Machine v0.3.0, scp was introduced to copy files from one Docker machine to another. This is very convenient if you want copying a file from your local computer to a remote Docker machine such as AWS EC2 or Digital Ocean because Docker Machine is taking care of SSH credentials for you.

Save you images using docker save like: docker save -o docker-images.tar app-web Copy images using docker-machine scp docker-machine scp ./docker-images.tar remote-machine:/home/ubuntu

Assume your remote Docker machine is remote-machine and the directory you want the tar file to be is /home/ubuntu.

Load the Docker image docker-machine ssh remote-machine sudo docker load -i docker-images.tar


why not just 'scp ' ?
K
Kaveh Naseri

The best way to save all the images is like this :

docker save $(docker images --format '{{.Repository}}:{{.Tag}}') -o allimages.tar

Above code will save all the images in allimages.tar and to load the images go to the directory where you saved the images and run this command :

docker load -i allimages.tar

Just make sure to use this commands in power shell and not in cmd


T
Tarek Kalaji

The fastest way to save and load docker image through gzip command:

docker save <image_id> | gzip > image_file.tgz

To load your zipped image on another server use immediate this command, it will be recognized as zipped image:

docker load -i image_file.tgz

to rename, or re-tag the image use:

docker image tag <image_id> <image_path_name>:<version>

for example:

docker image tag 4444444 your_docker_or_harbor_path/ubuntu:14.0

There is missing > after gzip. Proper command template: docker save <image_id> | gzip > image_file.tgz
V
Vikram

I want to move all images with tags.

```
OUT=$(docker images --format '{{.Repository}}:{{.Tag}}')
OUTPUT=($OUT)
docker save $(echo "${OUTPUT[*]}") -o /dir/images.tar
``` 

Explanation:

First OUT gets all tags but separated with new lines. Second OUTPUT gets all tags in an array. Third $(echo "${OUTPUT[*]}") puts all tags for a single docker save command so that all images are in a single tar.

Additionally, this can be zipped using gzip. On target, run:

tar xvf images.tar.gz -O | docker load

-O option to tar puts contents on stdin which can be grabbed by docker load.


r
runxc1 Bret Ferrier

If you are working on a Windows machine and uploading to a linux machine commands such as

docker save <image> | ssh user@host docker load

will not work if you are using powershell as it seems that it adds an additional character to the output. If you run the command using cmd (Command Prompt) it will however work. As a side note you can also install gzip using Chocolatey and the following will also work from cmd.

docker save <image> | gzip | ssh user@host docker load

C
Chu

You may use sshfs:

$ sshfs user@ip:/<remote-path> <local-mount-path>
$ docker save <image-id> > <local-mount-path>/myImage.tar

o
ofir_aghai

1. Pull an image or a repository from a registry.

docker pull [OPTIONS] NAME[:TAG|@DIGEST]

2. Save it as a .tar file.

docker save [OPTIONS] IMAGE [IMAGE...]

For example:

docker pull hello-world
docker save -o hello-world.tar hello-world

Y
Yoshi

Based on the @kolypto 's answer, this worked great for me but only with sudo for docker load:

docker save <image> | bzip2 | pv | ssh user@host sudo docker load

or if you don't have / don't want to install the pv:

docker save <image> | bzip2 | ssh user@host sudo docker load

No need to manually zip or similar.


S
Syed Faraz Umar

Script to perform Docker save and load function (tried and tested):

Docker Save:

#!/bin/bash

#files will be saved in the dir 'Docker_images'
mkdir Docker_images
cd Docker_images
directory=`pwd`
c=0
#save the image names in 'list.txt'
doc= docker images | awk '{print $1}' > list.txt
printf "START \n"
input="$directory/list.txt"
#Check and create the image tar for the docker images
while IFS= read -r line
do
     one=`echo $line | awk '{print $1}'`
     two=`echo $line | awk '{print $1}' | cut -c 1-3`
     if [ "$one" != "<none>" ]; then
             c=$((c+1))
             printf "\n $one \n $two \n"
             docker save -o $two$c'.tar' $one
             printf "Docker image number $c successfully converted:   $two$c \n \n"
     fi
done < "$input"

Docker Load:

#!/bin/bash

cd Docker_images/
directory=`pwd`
ls | grep tar > files.txt
c=0
printf "START \n"
input="$directory/files.txt"
while IFS= read -r line
do
     c=$((c+1))
     printf "$c) $line \n"
     docker load -i $line
     printf "$c) Successfully created the Docker image $line  \n \n"
done < "$input"