<![CDATA[Proget Docker Documentation Postgresql]]>Hi there,

we are currently exploring artifact repositories and thus Proget as well. Sadly, the documentation is lacking in our view.

Here (https://docs.inedo.com/docs/installation/linux/docker-guide) it says, that the integrated database is postgres. However when using the connection string PROGET_SQL_CONNECTION_STRING, it seems that proget tries to connect to an MSSQL database.

Unhandled exception. System.ArgumentException: Keyword not supported: 'port'.
   at Microsoft.Data.SqlClient.SqlConnectionStringBuilder.GetIndex(String keyword)
   at Microsoft.Data.SqlClient.SqlConnectionStringBuilder.set_Item(String keyword, Object value)
   at System.Data.Common.DbConnectionStringBuilder.set_ConnectionString(String value)
   at Microsoft.Data.SqlClient.SqlConnectionStringBuilder..ctor(String connectionString)
   at Inedo.ProGet.SharedConfig.ProcessConnectionString(String connectionString) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E656337\Src\src\ProGet\Configuration\SharedConfig.cs:line 196
   at Inedo.ProGet.SharedConfig.Initialize(Boolean reloadFile) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E656337\Src\src\ProGet\Configuration\SharedConfig.cs:line 47
   at Inedo.ProGet.Service.Program.Main(String[] args) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E656337\Src\src\ProGet\Service\Program.cs:line 50
   at Inedo.ProGet.Service.Program.<Main>(String[] args)

What options does the docker image actually support. Not being able to connect to an external postgresql would be a showstopper for us.

Best regards
Adrian

]]>https://forums.inedo.com/topic/5800/proget-docker-documentation-postgresqlRSS for NodeTue, 21 Jul 2026 23:03:16 GMTTue, 21 Jul 2026 11:27:16 GMT60<![CDATA[Reply to Proget Docker Documentation Postgresql on Tue, 21 Jul 2026 21:59:24 GMT]]>Hi @a.sieger ,

I would push back on that "hard requirement" because it doesn't make any technical or business sense, and will only lead to support headaches just like this.

There is something wrong with your PostgreSQL server configuration, perhaps permission related, that's causing the database to not be created. The error cannot be logged in the database because it doesn't exist.

I would delete the database and start again, but verify you've created the database exactly as specified using the exact version supported:
https://docs.inedo.com/docs/installation/postgresql#external-postgres

Things like improper locales will cause errors.

Then, don't run ProGet detached (i.e. ommit -d) so you can get the console logs. That's where you will see database errors. You can also run the upgradedb command instead:
https://docs.inedo.com/docs/installation/linux/installation-upgrading-docker-containers#upgrading-the-database-only-optional

Please let us know what you find!

Hope that helps,
Alana

]]>https://forums.inedo.com/post/19884https://forums.inedo.com/post/19884Tue, 21 Jul 2026 21:59:24 GMT<![CDATA[Reply to Proget Docker Documentation Postgresql on Tue, 21 Jul 2026 13:58:42 GMT]]>Hi @atripp
while I did overlook that (all the other options were in the styled code blocks), I still have problems.

However, I get this error when accessing the UI:
055a3ebd-2305-432b-8082-9f88592de1f4-image.jpeg

I would have expected, that proget creates everything on its own, however only the table __InedoDb_DbSchemaChanges is created.

And yes, the external database is a hard requirement for us. Before actually considering on making the switch to proget and getting a license, this needs to work.

Best regards
Adrian

]]>https://forums.inedo.com/post/19883https://forums.inedo.com/post/19883Tue, 21 Jul 2026 13:58:42 GMT<![CDATA[Reply to Proget Docker Documentation Postgresql on Tue, 21 Jul 2026 12:24:50 GMT]]>Hi @a.sieger ,

Please note that we do not recommend an external PostgreSQL database. It performs slower, costs more to maintain, has a higher chance of outages, and tends to cause support headaches down the line. The database primarily stores package metadata and application configuration, doesn't take up much disk space, and it's not the business data that your DBAs would own.

That being said if you really insist on using one, then please refer to the Database Connection String section on the page you linked.

For the non-embedded PostgreSQL database backend, you will need to specify a «inedo-product»_POSTGRES_CONNECTION_STRING environment variable instead.

So you need to use PROGET__POSTGRES_CONNECTION_STRING

Thanks,
Alana

]]>https://forums.inedo.com/post/19880https://forums.inedo.com/post/19880Tue, 21 Jul 2026 12:24:50 GMT