Thanks @rhessinger!

@rhessinger Thank you for this, it worked. I was able to successfully login and setup new users and privileges etc.

Thank you @atripp !

Hi @karsten-meichsner_9039 , Oh wonderful! If you're able/interested to try it out, then we should easily be able to add a checkbox in the UI for it and send you a patch/prerelease to try. That's how many of the other options got added Alana

Hi @karsten-meichsner_9039, I haven't seen that error before, but based on the text ("ProxyAuthenticationRequired for layer"), I think that Clair is trying to download an external layer? Some container image manifests (especially Windows, but not entirely) will point to a URL outside of the registry. This is often done for licensing reasons. What this means is that, Clair (or the docker client) downloads the layers from a url instead of ProGet. I'm not familiar enough with container scanners (Clair) to know how they search for vulnerabilities; I believe it's done by looking at the packages installed on the system. Log4j is not a package installed on the system (I think), but a library used in some applications. Cheers, Steve

Hi @james-traxler_1560, I'm not really sure I totally understand the issue, or how to resolve it... but I'll explain how a GET manifest request to your URL would work. Basically, ProGet returns whatever manifest file you uploaded, or whatever was downloaded via the connector. We do not generate the manifest files, or pay attention to the Accept request header. I understand that application/vnd.docker.distribution.manifest.list.v2+json is a "fat manifest", which is basically a manifest that points to other manifests on different architectures. So you don't know exactly what image you'll get until you install it on the machine. So if you want to inspect layers, you would first need to decide which manifest to use, I guess Cheers, Alana

Hi @marc-ledent_9164 , This isn't something that our LDAP/AD integration supports on Linux at this time. It's possible using the Windows-version, which has an LDAP integration that uses different libraries (that only work on Windows). We do plan on rewriting the LDAP/AD integration with a different library, as to allow this level of customization, but it's not something we can do right away. It'll be later this year. Cheers, Alana

@atripp said in ProGet doesn't log package publisher from command line: 6.0.16-rc.1 It's working Thanks alot

Hi @gurdip-sira_1271, Yes, this will be released with Otter later today. Thanks, Rich

Hello We are not experts in Powershell and we discovered DSC at the same time and thanks to Otter and we thought it was great and that they integrated perfectly. Knowing that DSC may not have continuity we will be attentive to the news, especially with Powershell Core. Thanks to the alternatives you have given us to DSC, we will modify our scripts and continue testing and studying Otter, because it seems a very good tool for us. Thank you and greetings

Hi @Joseph-Saladino_7499 , Hmm, that's really weird; the next thing I would try is to just restart all the machines (including the BuildMaster server). That's easy to do and the issue might go away. It could be a software error in the Windows networking stack It's possible that there's some intermediate network device that's interfering. Router, QoS device, etc. That's harder to diagnose, and would require some tracing ... starting by making sure that the RST packet is actually being received on the BuildMaster server (that's usually what indicates the error message), and then figuring out what device is sending it, and why. Our code doesn't work at the packet-level, but if the remote server (Inedo agent) is where the RST packets are coming from, it likely has to do with some obscure Windows setting... maybe even firmware on the network card. But at least something to look at. Cheers, Alana

Thank you I have moved my server from 2012 R2 to 2022 and the issue is resolved now Thanks again for quick reply

Hi @marc-ledent_9164, There's really just one, and that's the artifacts (BuildMaster) or packages (ProGet). To configure server level shared storage, you'll want to configure: For BuildMaster, the Artifacts.BasePath value in Administration > Advanced Settings. For ProGet, the Storage.PackagesRootPath value in Administration > Advanced Settings. Do note that ProGet also allows configuration of storage at a feed level, which you can find on the Manage Feed page for each feed. Click change on the right side of the Disk Path property. This guide might be helpful: https://docs.inedo.com/docs/installation-high-availability-load-balancing

Hi @pegogif654_4423, We have some great blog posts about this for NuGet and you can apply the same concepts to UPACK and Docker. 5 Quick Tips for NuGet Versioning How to use CI/CD pipelines for your NuGet Packages I believe you are looking to use our Repackaging feature and Package Promotion. Please note that in free editions of ProGet, you can only use the ProGet UI to repackage (for Docker it is Add Virtual Tag) and promote packages and containers. The APIs require a paid edition. Hope this helps! Thanks, Dan

Hi @marc-ledent_9164, Thanks for letting us know this is now resolved. Thanks, Dan

Thanks a lot

We found the problem finally, we had to enable this option [image: 1652731085537-microsoftteams-image.png]

@kichikawa_2913 thanks for letting me know; well, if you see it come again, please do inform us. It may be a caching issue on Linux/containers, but hard to say

@atripp Hi hello after downloading scripting 2.01 i restart the server otter worked perfectly. thanks

@kichikawa_2913 we don't have a typical set-up per se, really A lot of set-ups are very simple, since the team is new to CI/CD, and they just have the BuildMaster server do everything. Others have dozens of build agents configured in a pool to service various teams, and use lots of shared configuration. Most are somewhere in the middle -- since they started simple, and gradually explored over time. That's generally what i'd start with -- tackle one pattern/team, then move on to the next and improve over time.