@Sigve-opedal_6476
Here is a solution
Create a network.
With that proget can reach inedo as they will be into the same network.
docker network create inedo-net

Inedo
docker run -d --name inedodb
--network inedo-net
-v ./inedo-data:/var/lib/postgresql/data
proget.inedo.com/productimages/inedo/inedodb:17.6

sudo chown 1000:1000 proget-database

Proget
docker run -d --name proget
--network inedo-net
-p 8624:80
-v ./proget-packages:/var/proget/packages
-v ./proget-backups:/var/proget/backups
-v ./proget-database:/var/proget/database
-e INEDO_DB_TYPE=inedodb
-e INEDO_DB_HOST=inedodb
-e INEDO_DB_USER=proget \
proget.inedo.com/productimages/inedo/proget:latest

I got also lot's of issue because the database directory must be empty.
I hope it will help you.

Hey,
I understand the license,
But regarding the error 500, I have no information, Proget do not provide enough logs to understand this point.
I think my blocking point is coming from that.
Regards

I'm currently lauching Proget 25.0.18 in AKS the pod start correctly
with those ouputs:

 upgradedb ProGet version is 25.0.18.12.                                                                                                                
upgradedb Current DB schema version is 25.0.18.12.  
but logs show:
proget info: Microsoft.AspNetCore.Hosting.Diagnostics[1]                                                                                               │
│ proget       Request starting HTTP/1.1 GET http://10.200.0.194:80/health - - -                                                                         │
│ proget info: Microsoft.AspNetCore.Hosting.Diagnostics[2]                                                                                               │
│ proget       Request finished HTTP/1.1 GET http://10.200.0.194:80/health - 500 673 application/json 15.1132ms                                          │
│ proget Running Failover Detection...                                                                                                                   │
│ proget Failover Detection completed.                                                                                                                   │
│ proget info: Microsoft.AspNetCore.Hosting.Diagnostics[1]                                                                                               │
│ proget       Request starting HTTP/1.1 GET http://proget.apps.uat-internal.swisstiming.com/ - - -                                                      │
│ proget info: Microsoft.AspNetCore.Hosting.Diagnostics[2]                                                                                               │
│ proget       Request finished HTTP/1.1 GET http://proget.apps.uat-internal.XXXXXXX.com/ - 200 5691 text/html;+charset=UTF-8 1.6095ms               │
│ proget info: Microsoft.AspNetCore.Hosting.Diagnostics[1]                                       

When I start the command in the pod

curl http://localhost/health
{
  "applicationName": "ProGet",
  "databaseStatus": "OK",
  "databaseStatusDetails": null,
  "extensionsInstalled": {
    "ProGet": "25.0.18",
    "Inedo.SDK": "3.1.0",
    "InedoCore": "3.0.6",
    "Azure": "3.1.2",
    "Google Cloud": "3.1.0",
    "Amazon AWS": "3.1.3"
  },
  "licenseStatus": "Error",
  "licenseStatusDetail": "License key has expired.",
  "versionNumber": "2025.18 (Build 12)",
  "releaseNumber": "25.0.18",
  "startTime": 1770974767402,
  "serviceStatus": "OK",
  "serviceStatusDetail": null,
  "replicationStatus": {
  "serverStatus": null,
  "serverError": null,
  "clientStatus": null,
  "clienterror": null,
  "incoming": [],
  "outgoing": []
}

My point is coming from the fact that I don't have any idea to inject the license key in the pod

I have a proget 25.0.18 connected to sql server. I setup dedicated pv and pvc for blobs and packages I do not have any error ate this stage. The InitContainer sequence

    initContainers:
        - name: upgradedb
          image: "proget.inedo.com/productimages/inedo/proget:25.0.18"
          command: ["/usr/local/proget/service/proget", "upgradedb"]
          env:
            - name: PROGET_SQL_CONNECTION_STRING
              valueFrom:
                secretKeyRef:
                  name: connection-string
                  key: sql-connection-string
            - name: PROGET_ENCRYPTION_KEY
              valueFrom:
                secretKeyRef:
                  name: encryption-key
                  key: encryption-key

The pod description shows me that the initcontainer never start

Init Containers:                                                                                                           
│   upgradedb:                                                                                                               
│     Container ID:                                                                                                          
│     Image:         proget.inedo.com/productimages/inedo/proget:25.0.18                                                     │
│     Image ID:                                                                                                              
│     Port:          <none>                                                                                                  
│     Host Port:     <none>                                                                                                  
│     Command:                                                                                                               
│       /usr/local/proget/service/proget                                                                                     
│       upgradedb                                                                                                            
│     State:          Waiting                                                                                                
│       Reason:       PodInitializing                                                                                        
│     Ready:          False                                                                                                  
│     Restart Count:  0                                                                                                     
│     Environment:                                                                                                           
│       PROGET_SQL_CONNECTION_STRING:

The main problem is that there is no log, so I'm not able to understand where the system failed. Is there a way to track the initcontainer.
Regards

Thank you.
Does it mean that I must stay with the SQL server version and do not migrate to the one with PostGres.

@Sigve-opedal_6476
Here is a solution
Create a network.
With that proget can reach inedo as they will be into the same network.
docker network create inedo-net

Inedo
docker run -d --name inedodb
--network inedo-net
-v ./inedo-data:/var/lib/postgresql/data
proget.inedo.com/productimages/inedo/inedodb:17.6

sudo chown 1000:1000 proget-database

Proget
docker run -d --name proget
--network inedo-net
-p 8624:80
-v ./proget-packages:/var/proget/packages
-v ./proget-backups:/var/proget/backups
-v ./proget-database:/var/proget/database
-e INEDO_DB_TYPE=inedodb
-e INEDO_DB_HOST=inedodb
-e INEDO_DB_USER=proget \
proget.inedo.com/productimages/inedo/proget:latest

I got also lot's of issue because the database directory must be empty.
I hope it will help you.

From the documentation, I understand that the latest version will use InedoDB. Since this database is a hardened version of PostgreSQL, is there any way to deploy it in a highly‑available StatefulSet configuration on Kubernetes?