Install with Podman quadlets¶
Use the quadlets when you run Podman with systemd instead of Docker Compose. They
are in the quadlets/ folder of
rag-docker 1.1.0
and run the same services as the compose file.
Prerequisites¶
- Podman with quadlet support and systemd user services on the deployment host
- An inference provider and API-key tooling as described in Install with Docker Compose
Configure¶
-
Create the environment file as described in Install with Docker Compose, for example as
/opt/rag/rag.env.No variable expansion
Podman doesn't expand
${…}references in environment files. WriteConnectionStrings__DefaultConnectionwith the literal database name, user and password instead of the${POSTGRES_…}references fromexample.env. -
Fill in the placeholders in the unit files:
Unit What to set api-gateway,dlq-consumer,ingestion,rag-database-migrations,valkey,web-gatewayEnvironmentFile=: replaceREPLACE_ME_WITH_PATH_TO_ENV_FILEwith the absolute path of your environment filegateway-databaseEnvironment=POSTGRES_PASSWORD/USER/DB: thePOSTGRES_*values of your environment filerag-databaseEnvironment=POSTGRES_PASSWORD/USER/DB: theDB_PASSWORD,DB_USERandDB_NAMEvaluesrabbitmqEnvironment=RABBITMQ_DEFAULT_PASS/USER: theMB_PASSWORDandMB_USERvaluesweb-gateway-migrationsEnvironment=ConnectionStrings__DefaultConnection=: the full connection string with literal valuesweb-gatewayPublishPort=8000:8080: change the host port if needed -
api-gateway,ingestionanddlq-consumershare the host folder/opt/rag-system/temp-uploadsfor uploaded files. Create it, or change theVolume=lines of all three units to another path. The container path must matchTEMP_UPLOAD_DIR(default/app/temp_data). -
Copy the units and reload systemd:
Start¶
Start the dependencies first, then the services:
systemctl --user start rag-database rabbitmq
systemctl --user start rag-database-migrations
systemctl --user start web-gateway api-gateway ingestion dlq-consumer
web-gateway requires gateway-database, valkey and web-gateway-migrations,
so systemd starts them first. The database and RabbitMQ units report ready only
once their health checks pass. web-gateway-migrations is a one-shot unit: it runs
on every start of web-gateway, applies pending migrations, and exits.
All units are installed into default.target, so they start with the user's
systemd instance. For them to start at boot without a login session, enable
lingering for the user: loginctl enable-linger <user>.
Check the installation with curl http://localhost:8000/version, as described in
Install with Docker Compose. Then
create a tenant and an API key.
Keep your values when you update¶
The quadlets carry your local values (env file path, credentials, port). When you replace them with the files of a newer release, apply your values again. The release notes list which lines changed.