docker-registry

Unable to push a plugin using docker plugin push command

由 喜欢而已 提交于 2019-12-31 00:01:48
问题 I am trying to develop a V2 plugin. I am able to to use the 'docker plugin create' and 'docker plugin enable' commands with my plugin configuration. However the 'docker plugin push' command fails with the following error [root@localhost plugin]# docker plugin push adityadani/pxd-plugin Error response from daemon: errors: denied: requested access to the resource is denied unauthorized: authentication required Here is my docker version Client: Version: 1.13.0-rc4 API version: 1.25 Go version:

Setting up a remote private Docker registry

由 人盡茶涼 提交于 2019-12-29 06:20:55
问题 I need some tips on setting up a 'remote private Docker registry'. README.md on Docker-Registry mainly focus on private registry running on the same host, does not specify how other machines can access it remotely (or maybe too complex to understand). So far I found these threads: Docker: Issue with pulling from a private registry from another server (Still an open thread, no solution offered. Further discussion on Github gives hint on proxy, but how does that work?) Create a remote private

docker registry v2 迁移至另外一个 registry v2

由 旧时模样 提交于 2019-12-26 23:26:06
【推荐】2019 Java 开发者跳槽指南.pdf(吐血整理) >>> 思路 采用 docker pull, docker tag, docker push 的方式完成迁移 用到的 docker registry v2 api 主要用到两种个 registry v2 api 获取镜像列表 curl 127.0.0.1:15000/v2/_catalog?n=5000 | jq -r '.repositories | .[]' > images-list.txt #5000指的列出来的个数 获取单个镜像 tag curl -q 127.0.0.1:15000/v2/production/www/tags/list | jq -r '.tags | .[]' 脚本实现 脚本如下 #!/bin/bash # filename speed-pull-push.sh set -e FIRST_REGISTRY=127.0.0.1:15000 SECOND_REGISTRY=10.10.5.7:5000 while read -r repo do for tag in `curl -s $FIRST_REGISTRY/v2/$repo/tags/list | jq -r '.tags | .[]'` do source_image=$FIRST_REGISTRY/$repo:$tag

Error response from daemon: getsockopt: connection refused

由 我与影子孤独终老i 提交于 2019-12-23 17:17:35
问题 When I try to pull an image from a private Docker Registry I get the error Error response from daemon: Get https://XX.XX.XX.XXX:5000/v1/_ping: dial tcp XX.XX.XX.XXX:5000: getsockopt: connection refused The docker registry is definitely listening on the correct port. Running ss --listen --tcp -n -p Gives the result State Recv-Q Send-Q Local Address:Port Peer Address:Port LISTEN 0 128 *:22 *:* LISTEN 0 128 :::22 :::* LISTEN 0 128 :::5000 :::* Does anyone have any suggestions for how to solve

Mirroring private docker registry

由 一曲冷凌霜 提交于 2019-12-23 12:28:42
问题 What is currently the recommended way to mirror a Private Docker Registry? Mirroring functionality is provided by official docker-registry image but only for the Public Registry. See documentation: "Beware that mirroring only works for the public registry. You can not create a mirror for a private registry." My use-case: A bigger development team that is working in an office with a limited network. They only pull docker images from registries. Pushing is occasional and handled by Jenkins box

Docker Login: Error when manually logging into private Registry

由 心已入冬 提交于 2019-12-22 05:11:41
问题 I can't manually log into my private GitLab Docker Registry from CLI: # docker login -u "${DOCKER_USER}" -p "${DOCKER_PASS}" "${DOCKER_URL}" error getting credentials - err: exit status 1, out: `Cannot autolaunch D-Bus without X11 $DISPLAY` System info: Ubuntu 18.04 docker-ce 18.03.1~ce~3-0~ubuntu (from official repo, without install script) There is no ~/.docker/config.json for any users and I'm executing the docker login as root. On Google, I just find recommendations to export DISPLAY ...

Unable to delete some untagged docker images due to conflict

由 浪子不回头ぞ 提交于 2019-12-21 17:24:40
问题 I am unable to explicitly delete some untagged docker images. Specifically, those with the tag <none> . If I run docker images -a I get something like this: <none> <none> 91e54dfb1179 3 months ago 188.3 MB <none> <none> d74508fb6632 3 months ago 188.3 MB <none> <none> c22013c84729 3 months ago 188.3 MB <none> <none> d3a1f33e8a5a 3 months ago 188.1 MB <none> <none> 4a5e6db8c069 3 months ago 125.1 MB <none> <none> 2c49f83e0b13 3 months ago However, when I type docker rmi -f 2c49f83e0b13 I get:

Docker push - net/http: TLS handshake timeout

由 狂风中的少年 提交于 2019-12-21 14:39:40
问题 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

how to tag image in docker registry v2

由 做~自己de王妃 提交于 2019-12-20 12:05:42
问题 We have logic in our CI-CD that tags (via REST) staging image to latest (if tests are successful). This worked on registry v1. now moved to v2 api, and I can't find in documentation how to "add" tags to existing image in registry..I'm in a step that can bring the "manifest" of some staging image, but not sure how to add tag and http-post it. tried to send the below input "tag": "staging","latest", "tag": ["staging","latest"], and more { "schemaVersion": 1, "name": "configservice", "tag":

Difference between 'image' and 'build' within docker compose

由 心不动则不痛 提交于 2019-12-20 09:52:16
问题 Please help me understand the difference between 'image' and 'build' within docker compose 回答1: image means docker compose will run a container based on that image build means docker compose will first build an image based on the Dockerfile found in the path associated with build (and then run a container based on that image). PR 2458 was eventually merged to allow both (and use image as the image name when building, if it exists). therobyouknow mentions in the comments: dockerfile: as a sub
订阅 docker-registry