Proget Installation as container with external Postgres

[hardik.turakhia]

Hello,
I am looking to achieve the following:
Using ProGet image (container) via docker compose, connecting to external (org) Postgres database
Adding snippet of docker compose, I made referring documentation and AI's help. However, was not successful is getting this to work properly.

Proget does start up but with its own internal database.
Requesting help to correctly setup

networks:
  proget: 
    driver: bridge
volumes:
  postgres-data:
    external: true
services:
  proget:
    image: proget.inedo.com/productimages/inedo/proget:latest
    container_name: proget
    restart: unless-stopped
    ports:
      - "8624:80"
    volumes:
      - ./proget-packages:/var/proget/packages
      - ./proget-database:/var/proget/database
      - ./proget-backups:/var/proget/backups
      - ./volumes/packages:/var/proget/packages
      - ./volumes/config:/var/proget/config
      - ./volumes/logs:/var/proget/logs
      - ./volumes/extensions:/var/proget/extensions
      - ./volumes/backups:/var/proget/backups
      - ./certs:/certs:ro
    depends_on:
      - db
    networks:
      - proget
    environment:
      # ASPNETCORE_HTTPS_PORT: "443"
      # ASPNETCORE_URLS: "https://*:443"
      # ASPNETCORE_Kestrel__Certificates__Default__Path: "/certs/proget.pfx"
      # ASPNETCORE_Kestrel__Certificates__Default__Password: "${SSL_CERT_PASSWORD}"
      PROGET_DB_TYPE: "PostgreSQL"
      # PROGET_POSTGRES_CONNECTION_STRING: Server=postgres;Port=5432;Database=proget;Password=Pass@123;Username=root;
      # PROGET_POSTGRES_CONNECTION_STRING: Host=${DB_SERVER_HOST};Port=${DB_SERVER_PORT};Database=${DB_NAME};Username=${DB_USERNAME};Password=${DB_PASSWORD};
      TZ: "${TZ}"
    healthcheck:
      test: ["CMD","curl","-k","https://localhost:443/health"]
      interval: 30s
      timeout: 10s
      retries: 5
      start_period: 60s
  db:   
     image: postgres:16
     container_name: postgres
     environment:
         POSTGRES_USER: ${DB_USERNAME}
         POSTGRES_PASSWORD: ${DB_PASSWORD}
         POSTGRES_DB: ${DB_NAME}
     networks:
         - proget
     volumes:
         - postgres-data:/var/lib/postgresql/data
     # Uncomment if you want to connect to DB
     ports:
     - "4001:5432"

[rhessinger]

Hi @hardik.turakhia,

When you say external (org) PostgreSQL database, are you referring to a PostgreSQL database you are already hosting in your network and the one that is in the docker compose was for testing? Or are you just trying to host PostgreSQL in a separate container than ProGet, but both controlled by that single Docker compose file? If you are not using HA/Load Balancing, we recommend using the Embedded database. In a HA/Load Balancing environment, we recommend using InedoDB.

If you are still planning to use an external PostgreSQL database (InedoDB or PostgreSQL directly), here are some things to get you started. First, only InedoDB or ProstgreSQL 17 is supported. With that said, your ProGet service in your compose file is not quite right. You have duplicate volumes and your environment variables are using unsupported keys. A good starting point for you should be to review our Docker Compose guide and our Docker guide. Based on that, here is a better ProGet service node that can get you started.

  pg:
    image: proget.inedo.com/productimages/inedo/proget:26.0.9
    container_name: proget
    restart: unless-stopped
    ports:
      - "8624:80"
    volumes:
      - ./proget-packages:/var/proget/packages
    networks:
      - proget
    environment:
      - PROGET_POSTGRES_CONNECTION_STRING: Server=postgres;Port=5432;Database=proget;Password=Pass@123;Username=root;
      - PROGET_ENCRYPTION_KEY: ${ENC_KEY}

I removed the volumes for database and backups since you are planning to use an external database. I'm also using ./proget-packages/ for the volume mount. You had duplicates specified in your volume mounts, so update that path if you want to store it elsewhere. Then you need to specify the connection string for your PostgreSQL database in the PROGET_POSTGRES_CONNECTION_STRING environment variable. Lastly, I added the encryption key environment variable. You can generate this initially using head -c16 /dev/urandom | xxd -p -c32, then you will want to make sure you do not change it going forward. That should be enough to get you up and running.

For other volumes you might want to use see our other volumes section in our Docker guide. For other supported environment variables, see our supported environment variables section in our Docker guide.

Thanks,
Rich