Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFE: Add to documentation how to push to docker registry V2 #887

Open
Andrei-Stepanov opened this issue Nov 27, 2019 · 0 comments
Open

RFE: Add to documentation how to push to docker registry V2 #887

Andrei-Stepanov opened this issue Nov 27, 2019 · 0 comments
Labels
area/documentation For all bugs related to documentation kind/enhancement New feature or request priority/p3 agreed that this would be good to have, but no one is available at the moment.

Comments

@Andrei-Stepanov
Copy link

Hello.
This is not a bug. Rather, ask to add add missing documentation.
At this moment the documentation say to use base64, and craft config.json. But. This approach works only for docker registry V1. This is really time consuming when you try all different variants of urls and protocols in config.json and --destination, but get all time the same error:

error checking push permissions -- make sure you entered the correct tag name, and that you are authenticated correctly, and try again: checking push permission for "docker-registry.company.com/osci/astepano_test:latest": creating push check transport for docker-registry.company.com failed: unsupported status code 401
  1. Update the doc, and add to existing example, and say it applies only to V1.

  2. Ridiculously, there is no example for how to push to V2. So, please add it.
    For V2, there is no need to use base64

{
    "auths": {
        "https://docker-registry.company.com/v2/": {
            "username": "ignore",
            "password": "token"
        }
    }
}

And add parameter example

--destination=docker-registry.company.com/namespace/image:tag
@cvgw cvgw added area/documentation For all bugs related to documentation kind/enhancement New feature or request priority/p3 agreed that this would be good to have, but no one is available at the moment. labels Dec 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation For all bugs related to documentation kind/enhancement New feature or request priority/p3 agreed that this would be good to have, but no one is available at the moment.
Projects
None yet
Development

No branches or pull requests

2 participants