Hello Lucas,

CF takes care of authenticating (when needed) with the Docker registry. No
need to run anything more than `cf push`.

The output you included suggests that this was a network error on your side
or Dockerhub was temporarily unavailable. If the problem persists, I'd
suggest trying to use the same image from Dockerhub with Docker itself. If
Docker works and CF doesn't, there may be a network connectivity issue with
PCF Dev and/or Virtualbox.


On Fri, Aug 18, 2017 at 10:00 AM, lucas.reginato <lucas.reginato(a)gmail.com>
wrote:

I was taking a look into the error message and how to login to
registry-1.docker.io.
In order to properly login, we need to follow the details of this webpage:
https://docs.docker.com/registry/spec/auth/token/#requesting-a-token

In a high level:
- need to get a token at https://auth.docker.io/token with some query
parameters.
- then do the login again at registry-1.docker.io.
- and then proceed to the next operations.

Do we know if these steps are executed while pushing a docker image by PCF
Dev?

Thanks,

-Lucas



--
View this message in context: http://cf-dev.70369.x6.nabble.
com/Cf-fails-to-push-a-docker-image-tp7761p7767.html
Sent from the CF Dev mailing list archive at Nabble.com.

--
George Lestaris
GrootFS <https://www.github.com/cloudfoundry/grootfs> Product Manager, Cloud
Foundry <https://www.cloudfoundry.org/>, Pivotal <https://www.pivotal.io/>