docker-registry

How to create docker registry mirror

由 青春壹個敷衍的年華 提交于 2019-12-06 16:01:40
I use MAC OS X.And I want to use mirror in this tutorial , its step 1 is need to do this: docker --registry-mirror=http://<my-docker-mirror-host> -d But, when I use this command in terminal, it did't work: flag provided but not defined: --registry-mirror See 'docker --help'. then, I use the other way in tutorial: you may be able to add the --registry-mirror options to the DOCKER_OPTS variable in /etc/default/docker I don't know where to add this DOCKER_OPTS. I want to use mirror in client 1.7.0. Can anyone tell me how to set up the mirror?. I use this command to create mirror: docker run -d -p

Private Docker registry frontend with SSL encryption

由 痴心易碎 提交于 2019-12-06 16:01:31
I am using https://github.com/kwk/docker-registry-frontend for my private docker registry frontend. How to use this frontend with SSL encryption enabled if I have my files at /certs/domain.crt and /certs/domain.key ? There is one section https://github.com/kwk/docker-registry-frontend#ssl-encryption which talks about it but I'm not sure about following steps -v $PWD/server.crt:/etc/apache2/server.crt:ro \ -v $PWD/server.key:/etc/apache2/server.key:ro \ I'm not using apache. I simply have my crt and key at location mentioned above. How to use it these two at above two steps? It would be good if

Using Docker API to push to private registry

由 流过昼夜 提交于 2019-12-06 15:33:15
What is the syntax to push an image to a private registry? From the documentation, I would expect the below to work: curl -X POST -i "http://localhost:2375/images/localhost:5000/oillio/my_app:1.0-SNAPSHOT/push" I can use the CLI to do this: docker push localhost:5000/oillio/my_app:1.0-SNAPSHOT This works fine. But I can't figure out what the syntax is to do this from the API. When I try the above, I get a status 500 response with the text "EOF" The tag needs to be as a parameter and not within the url: /images/<imageName>/push?tag=<tadName> Note that you will also need the X-Registry-Auth

Mesos cannot deploy container from private Docker registry

由 Deadly 提交于 2019-12-06 15:24:21
I have a private Docker registry that is accessible at https://docker.somedomain.com (over standard port 443 not 5000). My infrastructure includes a set up of Mesosphere, which have docker containerizer enabled. I'm am trying to deploy a specific container to a Mesos slave via Marathon; however, this always fails with Mesos failing the task almost immediately with no data in stderr and stdout of that sandbox. I tried deploying from an image from the standard Docker Registry and it appears to work fine. I'm having trouble figuring out what is wrong. My private Docker registry does not require

Kubernetes private docker registry - registry proxy doesn't work

由 谁说胖子不能爱 提交于 2019-12-06 08:47:11
问题 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

GitLab CI ssh registry login

由 白昼怎懂夜的黑 提交于 2019-12-06 06:48:23
问题 I have a GitLab project gitlab.com/my-group/my-project which has a CI pipeline that builds an image and pushes it to the project's GitLab registry registry.gitlab.com/my-group/my-project:tag . I want to deploy this image to Google Compute Engine, where I have a VM running docker. Easy enough to do it manually by ssh'ing into the VM, then docker login registry.gitlab.com and docker run ... registry.gitlab.com/my-group/my-project:tag . Except the docker login command is interactive, which is a

Docker private registry using selfsigned certificates

由 徘徊边缘 提交于 2019-12-06 05:56:12
问题 I want to run a private docker registry which is widely available. So I will be able to push and pull images from other servers. I'm following this tutorials: doc1 & doc2 I performed 3 steps: First I've created my certificate and key (as CNAME I filled in my ec2-hostname) mkdir -p certs && openssl req \ -newkey rsa:4096 -nodes -sha256 -keyout certs/domain.key \ -x509 -days 365 -out certs/domain.crt Than I've created my docker registry, using this key. docker run -d -p 5000:5000 --restart

Batch docker registry manifest deletion: How to list manifests via v2 REST api?

由 余生长醉 提交于 2019-12-06 05:46:46
问题 I would like to delete particular or all manifests in my private docker registry remotely (v2 api) to make it possible images data to be collected by gc. I found this tool, but it only works with tags. I decided to extend it. I would like to enumerate manifests. Is it possible to get manifests list? I can't find something useful on this. I checked those and I'm also searching the web, but with no success. https://docs.docker.com/registry/spec/api/ https://docs.docker.com/registry/garbage

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

由 与世无争的帅哥 提交于 2019-12-06 03:59:54
问题 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

docker is using the v1 registry api when it should use v2

由 不想你离开。 提交于 2019-12-05 10:15:30
I'm trying to use a self hosted docker registry v2. I should be able to push a docker image, which does work locally on the host server (coreos) running the registry v2 container. However, on a separate machine (also coreos, same version) when I try to push to the registry, it's try to push to v1, giving this error: Error response from daemon: v1 ping attempt failed with error: Get https://172.22.22.11:5000/v1/_ping: dial tcp 172.22.22.11:5000: i/o timeout. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-registry 172.22.22.11:5000` to
订阅 docker-registry