missing vctl login?

[hermanccw]

we do host our internal container image in our private repository, is there an equivalent of docker login for vctl?

I am getting:

+ vctl pull <internal_docker_repo>/docker/ruby-dev:2.4.9-alpine
INFO Pulling from <internal_docker_repo>/docker/ruby-dev:2.4.9-alpine
───   ──────   ────────
REF   STATUS   PROGRESS
───   ──────   ────────
ERROR failed to resolve reference "<internal_docker_repo>/docker/ruby-dev:2.4.9-alpine": failed to authorize: failed to fetch anonymous token: unexpected status: 403 Forbidden

[jeffwubj]

yes, that's missing for now

[jorgemoralespou]

@jeffwubj be careful if implementing a vctl login command as Docker only logins to regiestries, vctl could potentially login to many different places (image registry, kubernetes clusters, ...). I don't think that in this case a 1-1 command with Docker will make sense.

[Blizzardo1]

Then how can I prevent the following message? ERROR failed to resolve reference "index.docker.io/library/hello:latest": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed

[mikeroySoft]

Then how can I prevent the following message? ERROR failed to resolve reference "index.docker.io/library/hello:latest": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed

What command are you running to get that output?

[Blizzardo1]

vctl run hello

[mikeroySoft]

Have you tried vctl run hello-world after vctl pull hello-world?

[Blizzardo1]

So it was my fault for not getting the container name correct. My bad. 👍

[jjarava]

Is there a way to load an image I can otherwise get from a repository? Or is the only option for now to pull from an existing, non-authenticated, repository (that would make it unworkable in my case unfortunately)