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:

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

Thanks for bringing this to our attention. This looks like a change will will need to make to the InedoDB container. Let me do some digging and I'll have an update for you soon.

Thanks,
Rich

After digging into this further, there are a handful of issues that have all hit here. Before I dive into these, is there a reason you chose to use InedoDB over using the embedded database? Our guidance is when using a single ProGet container, use the embedded database. InedoDB is only recommended to be used with clustered installations of ProGet.

In your case for using InedoDB and ProGet, there were basically 3 main issues that occurred.

Issue 1:
Your docker compose file is not quite correct. You currently have your volume mappings backwards which will cause your data to not be persisted through restarts. This is also why when you updated the the pg_hba.conf file, it did not persist. I should also point out there was a typo in our DockerFile, which pointed to the wrong directory for an InedoDB volume path. This is fixed in InedoDB 17.10.2. We also updated our InedoDB Docker Installation Docs to include the volume as well.

Here is a modified version of your docker compose that will fix these issues:

services:
  inedodb:
    image: proget.inedo.com/productimages/inedo/inedodb:17.10.2
    container_name: inedodb
    restart: unless-stopped
    ports:
      - "5432:5432"
    volumes:
      - /mnt/volume_nyc1_proget/postgres:/var/lib/inedodb

  proget:
    image: proget.inedo.com/productimages/inedo/proget:26.0.5
    container_name: proget
    restart: unless-stopped
    depends_on:
      - inedodb
    ports:
      - "8634:80"
    environment:
      PROGET_POSTGRES_CONNECTION_STRING: Host=inedodb;Port=5432;Database=proget;Username=inedodb;Password=<REDACTED>
    volumes:
      - /mnt/volume_nyc1_proget/proget/packages:/var/proget/packages
    deploy:
      resources:
        limits:
          memory: 2g

Issue 2:
The default for pg_hab.conf was too restrictive. This was actually updated in the Windows installer, but not in the inedodb create --name=proget command. This has now been fixed in InedoDB 17.10.2 and it will work out of the box. With that said, it is stored in a persisted volume, so changes will stay in affect. The other part of this is that when create a database, the container needs to be restarted. We have now added a message in the inedodb create command to restart the container.

Issue 3:
The connection string confusion. This is a side effect of Docker. When we generate the connection string in InedoDB, we use the get host name command from within the container. That hostname does not match the container name or network alias of the InedoDB . We have now added a warning when creating a database in InedoDB on Docker that you may need to update the host in the connection string.

With all those addressed in docs and InedoDB 17.10.2, you should be good to create a new ProGet instance with InedoDB. If you have already started adding packages using your existing setup, I would be worried that your database and package files are not persisting through restarts. I would recommend:

1. Set up a new instance using the DockerFile I used above and a trial key
2. Import your packages from that instance to the new instance
3. Shut down you old instance and move the license key to the new instance

I know this is kind of long, so if you are confused on anything or have any other questions, please let me know!

Thanks,
Rich