Thanks a lot @atripp for the quick fix. Problem solved Cheers -Fritz

Thanks for the heads up @felfert ! Looks like we're back now, looks like there was some issue reporting the outage on our end :) Alana

@gdivis Too bad I already changed all my keys and updated a lot of Test-VM-Instances in an internal OpenStack. Would have been be MUCH less work. Oh well. Thanks anyway for the info -Fritz

@rhessinger Well, after restarting with the 2025.14 image that I pulled this morning, now the warning is gone. Guess this was some outlier then ... Thanks -Fritz

Thanks @felfert it was an easy add, so look out for PG-3106 in the next maintenance release!

@gdivis That was the missing information (wait 30sec AND fetch repodata) - it works as described. To summarize what lead me to incorrectly assume that it was not fixed: My initial expectation was, it would be fixed by merely updating proget After that did not show progress, I found the repodata files in the feed storage path having an old timestamp Then I deleted and re-uploaded the latest rpm and noticed no timestamps change I never tried to actually fetch repodata, because I saw the old timestamps Thanks again for your clarification -Fritz

Hi @inedo_1308, I have just published a new CI build that should fix your issue. If you upgrade your Docker container to ProGet 25.0.8-ci.3, that should fix the problem with your feed usage instructions. Thanks, Rich

Hi Fritz, We appreciate the feedback on this! ProGet 2025 will indeed have a separate dedicated mount for the database, but we didn't include this in the preview. As to the other issues, yes we do have a supervisor that attempts to start postgres and perform a clean shutdown on container stop... but there are some bugs we are working through, likely made worse by the ownership issues you discovered. These concerns will absolutely be addressed before launch. Again, thanks for trying it out and please let us know of any other issues you find or suggestions you may have! -Greg

Many thanks, Alana! I can confirm, that the proget:24.0.37-ci.2 container image works like a charm Thanks for the quick fix! Fritz