locked
Unable to use Private Repository from Docker Hub RRS feed

  • Question

  • I have uploaded a container I currently have set to public b/c I was unable to get Azure to pull a private image from Docker Hub. Looking at the logs, it seems the login process fails. I have copy/pasted the error logs. The final lines I believe were from after I set it to public.

    I would really like to be able to use private registries, but whenever I try to set it as private the pull process fails.

    "docker login" requires at most 1 argument(s).
    See 'docker login --help'.

    Usage:  docker login [OPTIONS] [SERVER]

    Log in to a Docker registry
    "docker login" requires at most 1 argument(s).
    See 'docker login --help'.

    Usage:  docker login [OPTIONS] [SERVER]

    Log in to a Docker registry
    "docker login" requires at most 1 argument(s).
    See 'docker login --help'.

    Usage:  docker login [OPTIONS] [SERVER]

    Log in to a Docker registry
    "docker login" requires at most 1 argument(s).
    See 'docker login --help'.

    Usage:  docker login [OPTIONS] [SERVER]

    Log in to a Docker registry
    "docker login" requires at most 1 argument(s).
    See 'docker login --help'.

    Usage:  docker login [OPTIONS] [SERVER]

    Log in to a Docker registry
    "docker login" requires at most 1 argument(s).
    See 'docker login --help'.

    Usage:  docker login [OPTIONS] [SERVER]

    Log in to a Docker registry
    2017-03-08T20:25:25.553092045Z npm info it worked if it ends with ok
    2017-03-08T20:25:25.554473554Z npm info using npm@4.1.2
    2017-03-08T20:25:25.556281049Z npm info using node@v7.7.1
    2017-03-08T20:25:26.073045639Z npm info lifecycle boxett-frontend@1.0.0~prestart: boxett-frontend@1.0.0
    2017-03-08T20:25:26.090507604Z npm info lifecycle boxett-frontend@1.0.0~start: boxett-frontend@1.0.0

    Friday, March 10, 2017 3:21 PM

Answers

  • This conversation was continued here.

    Root cause for this particular issue is a bug on the App Service side preventing some users from pulling custom images from private repositories. A fix is in the works; no ETA at this point.

    • Proposed as answer by Nick Walker Wednesday, March 22, 2017 7:37 PM
    • Marked as answer by mraumer Friday, March 24, 2017 2:51 AM
    Wednesday, March 22, 2017 7:36 PM

All replies

  • How exactly are you attempting to pull a private image from the Docker Hub? Are you referring to any Azure documentation for the steps?

    Check the threads below which discusses on similar query:

    Allow pulling images from private repositories #232

    Can't pull image from private docker registry #1381

    If you haven’t checked this already, you may check the documentation on How to use a Docker image from a private image registry

    Saturday, March 11, 2017 2:53 PM
    Owner
  • I had read every one of those instructions and links prior to posting. Thank you, though.

    I switched the container on Docker Hub to public and was able to successfully pull the image. However, as this is protected work that is not a tenable solution. When I switched back this morning I got these errors in my error log, again from the docker error logs:

    ---

    "docker login" requires at most 1 argument(s).
    See 'docker login --help'.

    Usage:  docker login [OPTIONS] [SERVER]

    Log in to a Docker registry
    "docker login" requires at most 1 argument(s).
    See 'docker login --help'.

    Usage:  docker login [OPTIONS] [SERVER]

    Log in to a Docker registry
    "docker login" requires at most 1 argument(s).
    See 'docker login --help'.

    Usage:  docker login [OPTIONS] [SERVER]

    Log in to a Docker registry
    "docker login" requires at most 1 argument(s).
    See 'docker login --help'.

    Usage:  docker login [OPTIONS] [SERVER]

    Log in to a Docker registry
    "docker login" requires at most 1 argument(s).
    See 'docker login --help'.

    Usage:  docker login [OPTIONS] [SERVER]

    Log in to a Docker registry
    "docker login" requires at most 1 argument(s).
    See 'docker login --help'.

    Usage:  docker login [OPTIONS] [SERVER]

    Log in to a Docker registry

    ----

    Having re-read the links you provided to GitHub discussions regarding kitematic, the only potentially relevant takeaway is that Kitematic doesn't support private repos and that somehow affect Azure deployments pointing to private Docker repositories?

    Monday, March 20, 2017 2:11 PM
  • Sorry for not directly answering your opening questions:

    I am attempting to pull the private image to Docker Hub to my Web App for Linux container by way of the Azure Portal -> Settings -> Docker Container UI options. I select Docker Hub button, then Private button, and enter in all of my verified-to-be-working credentials.

    And, I have been referring to every scrap of documentation I can find.

    Based on the error, and the fact I get the exact same error when attempting to use the generic private registry option and manually plugging in the Docker Hub info there, I believe the issue is in the way Azure queries the service. The error seems to imply it's using the Docker CLI which on login first only prompts for username, not password, but both are being passed in. That's just a wild guess based on how I've been able to reproduce the exact error locally.

    • Edited by mraumer Monday, March 20, 2017 2:28 PM update
    Monday, March 20, 2017 2:26 PM
  • This conversation was continued here.

    Root cause for this particular issue is a bug on the App Service side preventing some users from pulling custom images from private repositories. A fix is in the works; no ETA at this point.

    • Proposed as answer by Nick Walker Wednesday, March 22, 2017 7:37 PM
    • Marked as answer by mraumer Friday, March 24, 2017 2:51 AM
    Wednesday, March 22, 2017 7:36 PM