I actually figured this out; sharing here for anyone else who might need it!

There's a config file that needs to be modified in the container to allow the defined user to connect from anywhere (please make sure you handle security appropriately!):

docker exec 564 <CONTAINER> -c 'echo -e "\nhost all inedodb 0.0.0.0/0 md5" >> /var/lib/inedodb/data/pg_hba.conf'

Since this is inside the container, it will be overwritten by docker compose down -- so if there is a more ideal configuration, feel free to update the thread. If you're setting up from scratch like I did, the steps are:

• docker compose up -d to create the containers
• The docker exec command in the Postgres docs to init the DB and create the connection string
• Editing docker-compose.yml with the connection string
• docker compose down <PROGET_CONTAINER> && docker compose up -d to remake the app container

I actually figured this out; sharing here for anyone else who might need it!

There's a config file that needs to be modified in the container to allow the defined user to connect from anywhere (please make sure you handle security appropriately!):

docker exec 564 <CONTAINER> -c 'echo -e "\nhost all inedodb 0.0.0.0/0 md5" >> /var/lib/inedodb/data/pg_hba.conf'

Since this is inside the container, it will be overwritten by docker compose down -- so if there is a more ideal configuration, feel free to update the thread. If you're setting up from scratch like I did, the steps are:

• docker compose up -d to create the containers
• The docker exec command in the Postgres docs to init the DB and create the connection string
• Editing docker-compose.yml with the connection string
• docker compose down <PROGET_CONTAINER> && docker compose up -d to remake the app container

I'm running Docker on Ubuntu 24.04, and I'm trying to stand up ProGet from scratch via Docker compose using your inedodb Postgres container. The containers run, the DB seems happy (I initialized the DB and got the connection string) -- but the app can't seem to find the DB until I swap the host in the DB connection for the container name. However, I get the following error when that happens:

Cannot connect to database; will retry in 1 second... Full error: 28000: no pg_hba.conf entry for host "172.18.0.3", user "inedodb", database "proget", no encryption

For what it's worth, I can't auth to the DB on the CLI inside the container with the creds from the connection string. That looks like:

563150413e94:/# psql -U inedodb -d proget
Password for user inedodb:
psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: password authentication failed for user "inedodb"

Any help would be greatly appreciated!

services:
  inedodb:
    image: proget.inedo.com/productimages/inedo/inedodb:17.6
    restart: unless-stopped
    ports:
      - "5432:5432"
    volumes:
      - /var/proget/database:/mnt/volume_nyc1_proget/postgres
      - /var/proget/backups:/mnt/volume_nyc1_proget/postgres

  proget:
    image: proget.inedo.com/productimages/inedo/proget:latest
    restart: unless-stopped
    depends_on:
      - inedodb
    ports:
      - "8624:80"
    environment:
      PROGET_POSTGRES_CONNECTION_STRING: Host=inedodb-1;Port=5432;Database=proget;Username=inedodb;Password=<REDACTED>
        #      PROGET_POSTGRES_CONNECTION_STRING: Host=193433396f00;Port=5432;Database=proget;Username=inedodb;Password=<REDACTED>
    volumes:
      - proget-packages:/mnt/volume_nyc1_proget/proget/packages
      - proget-extensions:/mnt/volume_nyc1_proget/proget/extensions
    deploy:
      resources:
        limits:
          memory: 2g

volumes:
  proget-packages:
  proget-extensions: