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 docker container has no access to packages on file system

    Scheduled Pinned Locked Moved Support
    4 Posts 3 Posters 18 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.
    • M Offline
      m.schindler_7799
      last edited by

      Hi,

      I had to re-install our proget server ( postgresql container, proget:latest ). Access to web ui works and our feeds and packages are listed. But when I try to download a package I get an error 'Cannot find the package in the package store.' In Manage Feed view the package path is correct: /var/proget/packages/.nugetv2/F2
      In file system all packages exist.

      docker run -d -v proget-packages:/var/proget/packages ....

      Any ideas? How can I check if proget uses correct package path? Any log files th check?

      Best regards,
      Markus

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

        Hi Markus,

        The package metadata records are in the database, but the files are on disk.

        The error is thrown when the operating system reports file-not-found when loading a file.

        Why is the operating system reporting that, it's hard to say. With Docker, there are two things to consider:

        • The package store (typically Admin > Advanced Settings > Root Package Store) refers to files within the container
        • The docker run -v command maps a directory outside of the container to one within the container

        Perhaps the directory outside of the contaienr doesn't have the file, or is a typo or something? Please let us know what you find...

        Hope that helps.
        Alana

        1 Reply Last reply Reply Quote 0
        • M Offline
          m.schindler_7799
          last edited by

          Hi Alana,

          thank you for your answer. I solved the problem. It was a mistake on volume mapping.

          Right command is: docker run -d -v /var/proget/packages:/var/proget/packages ....

          In your online installation guide its configured to use package store within container.

          Best regards,
          Markus

          1 Reply Last reply Reply Quote 0
          • gdivisG Offline
            gdivis inedo-engineer
            last edited by

            We've clarified the instructions for mounting the packages volume. In short, both formats will persist packages beyond the container's lifetime, but if you already have packages stored somewhere, you'll need to mount that directory (as you discovered) instead of using the "proget-packages" Docker volume.

            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