@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.

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

Hello,
Following your idea, I have done a test with wrong api call to remove a user from a group and I got an error into Proget Diagnostic Center. This stage confirm that I reach the correct server. I remove the error and the server answer me 200 but the user is still there.
I'm using Proget version 2025.26 (Build 11).
The apikey to do such operation is the admin one.
The url xxx/api/security/groups/update
The body of my request was

{
  "users": [
    "username"
  ],
  "name": "group"
}

The server answer is
VERBOSE: WebRequest: v1.1 POST https://mydomain/api/security/groups/update with application/x-www-form-urlencoded payload with body size 109 B (109 bytes)
VERBOSE: WebResponse: 200 OK with body size 0 b (0 bytes).
How can I trust a server which is not able to accomplish a task.
I can do it manually and with pgutil.

@atripp
Thanks for your quick answer.
I checked the name and it's correct, I was able to find it into the proget portal.
I also check the Diagnostics Center but not error appear.
Do I need to add simple or double quote around the name?
Does pgutil a better option the api?

Hello,
I'm using the ProGet api endpoint DELETE /api/security/users/delete?user=«username» to delete a user. Although the request return a 200 OK response, the user is not removed and still appears in ProGet.

I changed my storage account, but the connection string has been saved into table [dbo].[Feeds] PackageStoreConfiguration_Xml using AES-128 encryption. Is there a tool in ProGet to encrypt my connection string?

Hello,

We currently have a pipeline dedicated to detecting dependency confusion, but it takes around six hours to scan all artifacts. Does Inedo provide a native API or built-in capability to perform the same kind of analysis?
Regards

Hello,
Thank you for all those information.
I setup the Proget25 into an UAT instance and my question is now more related to the Licence.
Can I use my current Production licence on both environment Prod and UAT or I have to get a new one. Limited perhaps

Subject: ProGet 25 Migration, Database, and High Availability Questions

Hello,
We are currently running ProGet 24.x on Azure Kubernetes Service (AKS).
We are planning to upgrade to ProGet 25.x, as we understand that Microsoft SQL Server support will be not supported by the end of the year.
We therefore have a few questions regarding this migration:

• Database migration:
  Do we need to migrate to the internal PostgreSQL database when upgrading to ProGet 25, or are other database options supported?

• High Availability:
  How is High Availability implemented in ProGet 25?
  Are there specific architecture recommendations for Kubernetes-based deployments or Windows?

• Platform support
  Has this High Availability setup been fully tested on Linux pods, or is it currently supported only on Windows-based deployments?

• Performance and load
  Our current workload ranges from 500 to 7,000 requests per minute.
  Can ProGet 25 handle this level of traffic reliably, and are there any recommended sizing or scaling guidelines?

Thank you in advance for your guidance.

“Thank you for your answer. However, could you provide more information regarding the InedoDB Docker user settings?
Do I need to run the container as root?
For example:
YAML
securityContext:
runAsUser: 0
runAsGroup: 0
allowPrivilegeEscalation: true
readOnlyRootFilesystem: false
Each time I try to setup other user the system regarding access right.
Show more lines
**Have you tested whether the InedoDB container can handle 600 requests per minute or more?

What happens if the InedoDB container crashes?
How long does it take to restart?”**

Which kind of action must be node if I user external-postgres?
Do you have scripts?
Do you provide support?

I'm facing a lot of issues while setting up InedoDB. Could you explain what to do if I want to use Microsoft Azure PostgreSQL instead?

Can I use my ProGet License Enterprise to setup for testing purpose an other instance of ProGet with the version 25.x. I need to be sure that the High Availabitly works with two pods connected ot External MS SQL or your dedicated PostGres?