-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Closed
Description
Error Message and Logs
No specific error and could not find logs. Issue occurs after creating a new resource in a project using the docker compose option to create a database with timescaledb, converting the service it creates in the deployment to a database just results in a new "service" being created when saving or deploying resulting in the converted server (Now DB service) never deploying.
Steps to Reproduce
- Create a new resource with docker compose. Here's a sample compose:
services:
timescaledb:
image: timescale/timescaledb-ha:pg17
environment:
- POSTGRES_DB=$POSTGRES_DB
- POSTGRES_USER=$SERVICE_USER_POSTGRES
- POSTGRES_PASSWORD=$SERVICE_PASSWORD_POSTGRES
volumes:
- timescaledb-data:/var/lib/postgresql/data
- Open the service it created (Settings)
- Click convert to database
- Navigate back to resource landing
- Click save (Notice how it just creates a new service - similar to the original that we converted in step 3)
- Or, deploy the instance (It will create a new service and deploy that instead of the converted DB from step 3)
Example Repository URL
No response
Coolify Version
4.0.0-beta.442
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
ubuntu-24.04
Additional Information
No response
Metadata
Metadata
Assignees
Labels
No labels