server-install

The first problem is a typo in the connection string: postgresql://user:user@172.20.0.1:5432/lcp?sslmode=disable. In Go code it should be postgres://user:user@172.20.0.1:5432/lcp?sslmode=disable.

We also need to pass the full connection string as the second argument to sql.Open. For now, the dbFromURI function returns user:user@172.20.0.1:5432/lcp?sslmode=disable, but we need postgres://user:user@172.20.0.1:5432/lcp?sslmode=disable, because pq is waiting for this prefix to parse it.

After fixing this, I was able to establish a connection using a minimal postgres client based on your code.

To try this yourself, start the server with the following command:

In short, OpenSSHUtils has been deprecated by Microsoft (as you've indicated) and is no longer required. It is not recommended that you attempt to install this.

If you explain to us what feature from OpenSSHUtils you require, we can help you with a workaround.

• Most likely you'll be able to find what you're looking for on the Windows OpenSSH Github Repo

Furthermore, this GitHub comment references most of the open issues regarding the deprecation. https://github.com/MicrosoftDocs/windowsserverdocs/issues/3400#issuecomment-658249949

This is not recommended, but I'm explaining it to give you a better understanding of custom modules. This can also be used if Install-Module is not available on your version of PowerShell.

Where can I find the nuget package?

You've actually already linked it (https://www.powershellgallery.com/packages/OpenSSHUtils/1.0.0.1). If you click on "Manual Download" you'll be able to manually download it.

Is having the psd1 and psm1 equivalent to having the nuget?

The psd1 is all you need to be able to use the module. You'll need to manually install it.

1. type $env:PSModulePath to determine the locations PowerShell looks for modules on your system. The recommended location is C:\Windows\system32\WindowsPowerShell\v1.0\Modules\ for system-wide use.

I don't see how this question is related to programming, maybe move it to ServerFault.

And it's not clear what you want to do exactly. You don't want to install an embedded CA within the IPA Server, but it's unclear if you're going to use an external CA or no CA at all. In the first case this means the IPA Server would still automatically update the certificates, while the second case means you would update yourself when it is necessary.

The best entry point is the Linux Domain Identity, Authentication, and Policy Guide

If you're not going to use any CA at all, see section 2.3.6 :

I was able to resolve the same issue following this other answer, basically by adding --sysctl net.ipv6.conf.lo.disable_ipv6=0 into my docker run ... command. I don't actually know why it needs to be there but my symptoms were the same as yours and this did the trick. Here is my full command for testing:

You can find more information about truncating a set here: https://www.aerospike.com/docs/operations/manage/sets/

As mentioned there, truncation is not durable in Aerospike Community.

In the Enterprise Edition, truncation is durable and preserves record deletions through a cold-restart. In the Community Edition, similar to record deletes, records in previously truncated sets are not durable and deletes can return through a cold-start.