Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Requested access to the resource is denied during docker push

    Scheduled Pinned Locked Moved Support
    proget
    2 Posts 2 Posters 51 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ? This user is from outside of this forum
      Guest
      last edited by

      We have a working version for proget basic edition serving as a docker repo among other things in one office location. I am trying to demonstrate the value of having it in other locations so we can move to the enterprise edition. I installed the latest free edition on VM in a second location and set it up to match what we have in the first.

      This setup includes using IIS on install; https binding with a cert for the proget site.
      I also ensured that the NetworkService has full control access to the feed storage location)

      When I try to push an image up to the repository I see this:
      The push refers to repository [docker.io/<server name>/<feed name>/library/redis]
      1694aef55adf: Preparing
      88d7964860e0: Preparing
      fc3dfaf386f6: Preparing
      3c187ef1bb50: Preparing
      8037c9e9008e: Preparing
      0ac4f5baf9b7: Waiting
      63c478d60b8e: Waiting
      bc06b22070cd: Waiting
      denied: requested access to the resource is denied

      The same failure happens using anonymous or for a user I have created on the proget site, given push and view access to; and have done a docker login on the client before trying the push.

      Any suggestions on what to try next?

      Product: ProGet
      Version: 5.1.20

      1 Reply Last reply Reply Quote 0
      • benB Offline
        ben inedo-engineer
        last edited by

        Hello Eric,

        I think Docker requires at least one . in the hostname, and it's trying to access the default Docker hub.

        Another way that might work would be to add the port number to the hostname:

        <server name>:443/<feed name>/library/redis

        (the library part is optional to match the Docker hub, so <server name>:443/<feed name>/redis should also work)

        1 Reply Last reply Reply Quote 0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        • 1 / 1
        • First post
          Last post
        Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation