如果有人正在寻找一种快速将所有图像推送到私有存储库的方法， 你可以使用我的bash脚本-它会将所有Docker映像推送到新的私有注册表:

#!/bin/bash

repo="<change_to_your_new_repo>"
remote_repo="<the_new_repo_name>"

for img in $(docker images --format "{{.Repository}}:{{.Tag}}")
do
        image=$(echo $img | cut -d ":" -f 1)
        image_tag=$(echo $img | cut -d ":" -f 2)

        docker image tag $image:$image_tag $repo/$remote_repo/$image:$image_tag
        docker image push $repo/$remote_repo/$image:$image_tag

        docker rmi $repo/$remote_repo/$image:$image_tag
done

以下是将Docker Image推送到DockerHub的私有存储库的步骤

1-首先使用命令检查Docker图像

码头工人的图片

2-查看Docker Tag命令帮助

Docker标签——救命

3-现在标记一个名称，以您创建的图像

DockerHubUser\Private-repoName:tagName(标签名可选。默认名称为最新)

4-在推送镜像到DockerHub Private Repo之前，请先使用命令登录DockerHub

docker login[提供dockerHub用户名和密码登录]

5-现在推Docker映像到您的私人回购使用命令

docker push [options] ImgName[:tag]例如docker push DockerHubUser\Private-repoName:tagName

6-现在导航到DockerHub Private Repo，你会看到Docker映像被推送到你的私有存储库上，在前面的步骤中名称写为TagName

裁判:dock.docker.com

介绍部署和配置注册表的基本信息

运行本地注册表

在部署注册表之前，需要在主机上安装Docker。

使用如下命令启动注册表容器:

start_registry.sh

#!/bin/bash

docker run -d \
  -p 5000:5000 \
  --restart=always \
  --name registry \
  -v /data/registry:/var/lib/registry \
  registry:2

从Docker Hub复制一个映像到注册表

Pull the ubuntu:16.04 image from Docker Hub. $ docker pull ubuntu:16.04 Tag the image as localhost:5000/my-ubuntu. This creates an additional tag for the existing image. When the first part of the tag is a hostname and port, Docker interprets this as the location of a registry, when pushing. $ docker tag ubuntu:16.04 localhost:5000/my-ubuntu Push the image to the local registry running at localhost:5000: $ docker push localhost:5000/my-ubuntu Remove the locally-cached images. This does not remove the localhost:5000/my-ubuntu image from your registry. $ docker image remove ubuntu:16.04 $ docker image remove localhost:5000/my-ubuntu Pull the localhost:5000/my-ubuntu image from your local registry. $ docker pull localhost:5000/my-ubuntu

Deploy a plain HTTP registry

根据docs.docker.com，这是非常不安全的，不建议。

Edit the daemon.json file, whose default location is /etc/docker/daemon.json on Linux or C:\ProgramData\docker\config\daemon.json on Windows Server. If you use Docker for Mac or Docker for Windows, click Docker icon -> Preferences -> Daemon, add in the insecure registry. If the daemon.json file does not exist, create it. Assuming there are no other settings in the file, it should have the following contents: { "insecure-registries" : ["myregistrydomain.com:5000"] } With insecure registries enabled, Docker goes through the following steps: First, try using HTTPS. If HTTPS is available but the certificate is invalid, ignore the error about the certificate. If HTTPS is not available, fall back to HTTP. Restart Docker for the changes to take effect.

只需简单的三步:

Docker登录——username用户名 如果你省略了——password，提示输入密码，这是推荐的，因为它不会存储在你的命令历史中 Docker标签my-image用户名/my-repo Docker推送用户名/my-repo

简单的工作解决方案:

访问这里https://hub.docker.com/创建一个私有存储库，例如johnsmith/ PRIVATE -repository，这是您在构建映像时将用于映像的name / repository。

首先，docker登录 其次，我使用“docker build -t johnsmith/private-repository:01 .”(其中01是我的版本名)来创建图像，并且我使用“docker images”来确认创建的图像，例如下面这个黄色框中的图像:(对不起，我不能粘贴表格格式，但只能粘贴文本字符串)

johnsmith/private-repository(REPOSITORY) 01(TAG) c5f4a2861d6e(IMAGE ID) 2 days ago(CREATED) 305MB(SIZE)

第三，我使用docker推送johnsmith/private-repository:01(你的私人回购将在这里的例子https://hub.docker.com/r/johnsmith/private-repository/)

完成了!

有两种选择:

Go into the hub, and create the repository first, and mark it as private. Then when you push to that repo, it will be private. This is the most common approach. log into your docker hub account, and go to your global settings. There is a setting that allows you to set what your default visability is for the repositories that you push. By default it is set to public, but if you change it to private, all of your repositories that you push will be marked as private by default. It is important to note that you will need to have enough private repos available on your account, or else the repo will be locked until you upgrade your plan.