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!

    Proget 2023 - docker manifest problem

    Scheduled Pinned Locked Moved Support
    7 Posts 2 Posters 21 Views 1 Watching
    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.
    • U Offline
      udi.moshe_0021
      last edited by

      Hello,

      i am using proget free v2023.
      i have created a container feed and attached him to docker hub connectors according to the urls in docker documentation. the connectors are healthy.
      the feed allows anonymous pulling and i have con figured the feed in docker as insecure registry.
      when i try pulling an image i always get manifest unknown error with\without doing docker login.
      i use a proxy to connect to the internet and i do not see any problem there. other feeds like npm works fine.

      10x

      atrippA 1 Reply Last reply Reply Quote 0
      • atrippA Offline
        atripp inedo-engineer @udi.moshe_0021
        last edited by

        Hi @udi-moshe_0021 ,

        I would suggest using the latest ProGet version.

        A "manifest unknown" is a very generic error, and the docker client doesn't log any more details (log, error message from ProGet, etc). I suggest using a traffic capture tool to see exactly what the problem is.

        Under the hood, Docker clients can have some problems with proxies, so this could be related. The DockerHub also has rate limiting, so that could be a problem you're experiencing. We just can't see it with just the Docker client sometimes.

        Thanks,
        Alana

        U 1 Reply Last reply Reply Quote 0
        • U Offline
          udi.moshe_0021 @atripp
          last edited by

          @atripp thank you very much.
          will try the update.

          thanks

          U 1 Reply Last reply Reply Quote 0
          • U Offline
            udi.moshe_0021 @udi.moshe_0021
            last edited by

            Hi @atripp ,
            i have successfully updated to the latest version 2024.19 and get the same error.
            i have created a lab in another computer connected directly to the internet (no proxy because i thought that maybe it is blocking something that i can't see) and got the same result. in the lab i used oracle linux 9.4 with podman instead of docker. upon pulling an image directly from docker, the image and the manifest are downloaded correctly.
            just to make sure it is possible, i can configure a docker feed and pair up to it docker connectors and it should pull images as proxy like other feeds such as npm, is it ?

            thanks

            U 1 Reply Last reply Reply Quote 0
            • U Offline
              udi.moshe_0021 @udi.moshe_0021
              last edited by

              Hi @atripp ,
              i have managed to successfully pull an image to proget.
              the syntax i used is like: "podman pull xxx:8625/docker/library/ubuntu"
              and this i discovered from the podman's response. when i tried looking up the additional "library" in the client setup of the feed or the documentation, i didn't find any thing related to that.
              i have tried replacing "library" with something else like "udi" and it didn't work.
              i then, tried to download fluent/fluent-id with the syntax "podman pull xxx:8625/docker/library/fluent/fluent-id" and it didn't work. i then deleted the "library" part and it worked.

              is this how it is suppose to work ?
              images without a prefix will need the "library" prefix ?

              thanks

              atrippA 1 Reply Last reply Reply Quote 0
              • atrippA Offline
                atripp inedo-engineer @udi.moshe_0021
                last edited by

                Hi @udi-moshe_0021 ,

                If you're talking about connecting to DockerHub, the behavior is a little weird... but yes, images without a prefix need the library prefix. This is actually how the Docker client behaves behind the scenes.

                When you request ubuntu, the Docker client actually requests library/ubuntu. You can edit the connector (Advanced tab) to automatically add the library prefix, which will behave like the Docker client.

                Thanks,
                Alana

                U 1 Reply Last reply Reply Quote 0
                • U Offline
                  udi.moshe_0021 @atripp
                  last edited by

                  Hi @atripp ,
                  found this config. i remember seeing it and left it checked because the description recommended it for registries like microsoft and for some reason i didn't pay attention to this until i figured out that i need to add "library" prefix.
                  thank you very much for all the help.

                  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