How to share my Docker-Image without using the Docker-Hub

Question

I m wondering where Docker s images are exactly stored to in my local host machine  Can I share my Docker-Image without using the Docker-Hub or a Dockerfile but the  real  Docker-Image  And what is exactly happening when I  push  my Docker-Image to Docker-Hub

User · Answer

Update  More recently  there is Amazon AWS ECR  Elastic Container Registry   which provides a Docker image registry to which you can control access by means of the AWS IAM access management service  ECR can also run a CVE  vulnerabilities  check on your image when you push it  Once you create your ECR  and obtain the  quot URL quot  you can push and pull as required  subject to the permissions you create  hence making it private or public as you wish  Pricing is by amount of data stored  and data transfer costs  https   aws amazon com ecr   Original answer  If you do not want to use the Docker Hub itself  you can host your own Docker repository under Artifactory by JFrog  https   www jfrog com confluence display RTF Docker Repositories which will then run on your own server s   Other hosting suppliers are available  eg CoreOS  http   www theregister co uk 2014 10 30 coreos enterprise registry  which bought quay io

User · Answer

Sending a docker image to a remote server can be done in 3 simple steps    Locally  save docker image as a  tar     docker save -o  lt path for created tar file gt   lt image name gt     Locally  use scp to transfer  tar to remote On remote server  load image into docker    docker load -i  lt path to docker image tar file gt

User · Answer

Docker images are stored as filesystem layers  Every command in the Dockerfile creates a layer  You can also create layers by using docker commit from the command line after making some changes  via docker run probably    These layers are stored by default under  var lib docker  While you could  theoretically  cherry pick files from there and install it in a different docker server  is probably a bad idea to play with the internal representation used by Docker   When you push your image  these layers are sent to the registry  the docker hub registry  by default    unless you tag your image with another registry prefix  and stored there  When pushing  the layer id is used to check if you already have the layer locally or it needs to be downloaded  You can use docker history to peek at which layers  other images  are used  and  to some extent  which command created the layer    As for options to share an image without pushing to the docker hub registry  your best options are    docker save an image or docker export a container  This will output a tar file to standard output  so you will like to do something like docker save  dockerizeit agent   gt  dk agent latest tar  Then you can use docker load or docker import in a different host  Host your own private registry  - Outdated  see comments See the docker registry image  We have built an s3 backed registry which you can start and stop as needed  all state is kept on the s3 bucket of your choice  which is trivial to setup  This is also an interesting way of watching what happens when pushing to a registry Use another registry like quay io  I haven t personally tried it   although whatever concerns you have with the docker hub will probably apply here too

User · Answer

Based on this blog  one could share a docker image without a docker registry by executing   docker save --output latestversion-1 0 0 tar dockerregistry latestversion 1 0 0   Once this command has been completed  one could copy the image to a server and import it as follows   docker load --input latestversion-1 0 0 tar

[docker] How to share my Docker-Image without using the Docker-Hub?

Examples related to docker

Examples related to docker-registry