-
Updated
May 30, 2020
通过了CSR认证,却没有获取到nodes的信息
[root@k8s-01 ssl]# kubectl get csr
NAME AGE REQUESTOR CONDITION
csr-b0gpz 6m kubelet-bootstrap Pending
csr-swnf0 27m kubelet-bootstrap Pending
[root@k8s-01 ssl]# kubectl certificate approve csr-b0gpz csr-swnf0
certificatesigningrequest "csr-b0gpz" approved
certificatesigningrequest "csr-swnf0" approved
[root@k8s-01 ssl]
Might need some changes like
uber/makisu#223
Unfortunately the installation instructions in the release notes for Windows will never work as it appears it's just a copy-n-paste from the linux/mac instructions.
As a windows user
I would like to install reg
On a Windows platform
Note - the windows binaries in the releases are actual windows executables so WSL is not really an option
Also, this tool installs as reg.exe which
The simplest and most complete UI for your private registry
It would be handy if it was documented how to supply a trust bundle from the host for registries with a private/self-hosted certificate known to the host
Should we look at using something like https://github.com/spf13/viper
One of the issues I keep having is trying to remember the environment vars that klar supports ;)
Something like viper would support command line flags, environment vars, config files, and would also be self-documenting (via --help).
Good idea?
Manifest tool for manifest list object creation/query
We need to clearly highlight API 1.X features in our documentation.
Before http 400
Nexus CLI version 1.0.0-beta
$ nexus-cli configure
Enter Nexus Host: http://nexus.host.local:9081
Enter Nexus Repository Name: docker
Enter Nexus Username: admin
Enter Nexus Password: admin123
$ nexus-cli image ls
parse http://nexus.host.local:9081/repository/docker/v2/_catalog: first path segment in URL cannot contain colon
IPFS-backed Docker Registry
We use catalogs in the registry as folders.
e.g. ${company}/${project}/${module} as catalog name.
The ui does actually list the subrepositories when selecting the Namespace ${catalog} and also corretly shows the tag count, but when clicking on that catalog it ends in a empty tag l
Docker has a global --config flag documented here: https://docs.docker.com/engine/reference/commandline/cli/
Through this, you can define the location of config.json.
docker-credential-gcr configure-docker currently always generates the config file in ~/.docker. It would be nice to be able to modify this in the same way as in Docker.
I try to issue `docker-credential-gcr configure
Docker image synchronization tool for Docker Registry V2 based services
Deckschrubber inspects images of a Docker Registry and removes those older than a given age.
I'm interesting in using the fast puller to download docker images from remote repositories to the local machine's docker daemon. I'm interesting in streaming the download into the docker daemon as fast as possible. I was hoping for an example to use something like https://github.com/bazelbuild/rules_docker/blob/master/container/incremental_load.sh.tpl in order to do so. Do you have anything simil
An HTTPS Proxy for Docker providing centralized configuration and caching of any registry (quay.io, DockerHub, k8s.gcr.io)
I wasn't able to delete until I started my private repo with this flag:
-e REGISTRY_STORAGE_DELETE_ENABLED="true"Maybe this could be noted in the readme?
Cleans up docker registry by removing untagged manifests from the registry
owasp-workshop: Orchetraing containers with Kubernetes
Build and push docker images caching each stage to reduce build time
Docker入门精华版
Fast Distribution of Docker Images on Clusters
Terraform Module to manage Docker Container Registries on AWS ECR
docker2nix currently only accepts a manifest on stdin or as a filesystem path via --manifest. Which works nicely if you have fetch and store the registry manifest separately from generating the Nix code but we can also make this easier to use by making both of those inputs optional and fetching the manifest for the user if they don't provide a manifest.
Add a description, image, and links to the docker-registry topic page so that developers can more easily learn about it.
To associate your repository with the docker-registry topic, visit your repo's landing page and select "manage topics."
Copied from briandealwis/cram#5: @student-06 asked