docker-registry | 易学教程

Docker: Refer to registry by ip address

阅读更多关于 Docker: Refer to registry by ip address

问题 I have a Docker image I want to push to my registry (hosted on localhost ). I do: docker push localhost:5000/my_image and works properly. However, if I tag the image and push it by: docker push 172.20.20.20:5000/my_image I get an error. The push refers to a repository [172.20.20.20:5000/my_tomcat] (len: 1) unable to ping registry endpoint https://172.20.20.20:5000/v0/ v2 ping attempt failed with error: Get https://172.20.20.20:5000/v2/: Gateway Time-out Can't I refer to registry by IP? If so,

Clone an image from a docker registry to another

阅读更多关于 Clone an image from a docker registry to another

问题 I have a private registry with a set of images. It can be visualized as a store of applications. My app can take these applications and run them on other machines. To achieve this, my app first pull the image from the private registry and then copies it to a local registry for later use. Step as are follow: docker pull privateregistry:5000/company/app:tag docker tag privateregistry:5000/company/app:tag localregistry:5000/company/app:tag docker push localregistry:5000/company/app:tag Then

How can I pass secret data to a container

阅读更多关于 How can I pass secret data to a container

问题 My Tomcat Container needs data that has to be well protected, i.e. passwords for database access and certificates and keys for Single Sign On to other systems. I´ve seen some suggestions to use -e or -env-file to pass secret data to a container but this can be discovered with docker inspect ( -env-file also shows all the properties of the file in docker inspect). Another approach is to link a data container with the secrets to the service container but I don´t like the concept of having this

Kubernetes private docker registry - registry proxy doesn't work

阅读更多关于 Kubernetes private docker registry - registry proxy doesn't work

I'm running Kubernetes on a 3 node setup (Core OS - setup from this guide - https://coreos.com/kubernetes/docs/latest/deploy-master.html ). I need to run a private docker registry in the setup, so I was following this guide: https://github.com/kubernetes/kubernetes/tree/master/cluster/addons/registry I think that the registry pod is running, at least there is an empty response from the registry pod on port 5000 (the guide says I should be getting a "404 Unauthorized" response). I'm testing this from a busybox, it even works with the dns hostname. But the main problem is that the kube-registry

Docker: TLS handshake timeout

阅读更多关于 Docker: TLS handshake timeout

问题 I've created my own private registry (private-registry) but I'm unable to push images to it. Than I get the following error: The push refers to a repository [private-registry:5000/ubuntu] (len: 1) unable to ping registry endpoint https://private-registry:5000/v0/ v2 ping attempt failed with error: Get https://private-registry:5000/v2/: net/http: TLS handshake timeout v1 ping attempt failed with error: Get https://private-registry:5000/v1/_ping: net/http: TLS handshake timeout The logs of the

Docker push - net/http: TLS handshake timeout

阅读更多关于 Docker push - net/http: TLS handshake timeout

I've deployed a private docker image registry on an AWS EC2 Ubuntu 14.04 instance. The registry is secured using Let's Encrypt certificate. Unfortunately, I'm getting net/http: TLS handshake timeout for docker push operations that take longer than 300s: This is the output of the time'd command: [luqo33@home-pc containers]$ time docker push <my-registry-domain:5000>/nginx The push refers to a repository [<my-registry-domain:5000>/nginx] dda5a806f0b0: Layer already exists ec35cfccb7f7: Layer already exists 94c1a232bb3f: Layer already exists 6d6b9812c8ae: Layer already exists 695da0025de6:

How should a .dockercfg file be hosted in a Mesosphere-on-AWS setup so that only Mesosphere can use it?

阅读更多关于 How should a .dockercfg file be hosted in a Mesosphere-on-AWS setup so that only Mesosphere can use it?

We have set up a test cluster with Mesosphere on AWS, in a private VPC. We have some Docker images which are public, which are easy enough to deploy. However most of our services are private images, hosted on the Docker Hub private plan, and require authentication to access. Mesosphere is capable of private registry authentication, but it achieves this in a not-exactly-ideal way: a HTTPS URI to a .dockercfg file needs to be specified in all Mesos/Marathon task definitions. As the title suggests, the question is basically: how should the .dockercfg file be hosted within AWS so that access may

How can I update full description on Docker Hub automatically?

阅读更多关于 How can I update full description on Docker Hub automatically?

问题 I'm using Travis CI for building docker images from Dockerfiles and then pushing them to the Docker Hub on success. I've created an MD file describing the image and how to use it. I want to have the same description on the Docker Hub in the full description section. As I may update the description in the future, I want to have Travis CI automatically update the description based on the MD file in the repository with the new image. Anyone knows how to do this? 回答1: Since the Docker Hub does

Docker: Refer to registry by ip address

阅读更多关于 Docker: Refer to registry by ip address

I have a Docker image I want to push to my registry (hosted on localhost ). I do: docker push localhost:5000/my_image and works properly. However, if I tag the image and push it by: docker push 172.20.20.20:5000/my_image I get an error. The push refers to a repository [172.20.20.20:5000/my_tomcat] (len: 1) unable to ping registry endpoint https://172.20.20.20:5000/v0/ v2 ping attempt failed with error: Get https://172.20.20.20:5000/v2/: Gateway Time-out Can't I refer to registry by IP? If so, how could I push an image from another host that it is not localhost ? EDIT I'm running the registry

Can I get an image digest without downloading the image?

阅读更多关于 Can I get an image digest without downloading the image?

问题 Similar to the question "What´s the sha256 code of a docker image?", I would like to find the digest of a Docker image. I can see the digest when I download an image: $ docker pull waisbrot/wait:latest latest: Pulling from waisbrot/wait Digest: sha256:6f2185daa4ab1711181c30d03f565508e8e978ebd0f263030e7de98deee5f330 Status: Image is up to date for waisbrot/wait:latest $ Another question, What is the Docker registry v2 API endpoint to get the digest for an image has an answer suggesting the