[Bug]: "coolify-db" container is just gone

[SeriousM]

Error Message and Logs

Since two days, the "coolify-db" container is periodically removed. I don't know why and who's triggering this.
The logs show: SQLSTATE[08006] [7] could not translate host name "coolify-db" to address: Name does not resolve

My guess is that the problem exists since the last update from v4.0.0-beta.451 to v4.0.0-beta.452.

To fix the issue I followed the troubleshooting guide and execute:

# su access to my /data/coolify/src needs su
sudo su

cd /data/coolify/source/
docker compose --env-file .env -f docker-compose.yml -f docker-compose.prod.yml up -d

The container is recreated and started. After that everything is working again.

Please help me to identify this problem.

Steps to Reproduce

1. update from v4.0.0-beta.451 to v4.0.0-beta.452
2. wait till morning
3. "coolify-db" container is removed

Example Repository URL

No response

Coolify Version

v4.0.0-beta.452

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Debian GNU/Linux 12 (bookworm)

Additional Information

No response

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and agent prompts for this issue.

• Create Plan

Examples

• Example 1
• Example 2

🔗 Similar & Duplicate Issues

Possible Duplicates

• coollabsio/coolify#6750

Related Issues

• coollabsio/coolify#6500
• coollabsio/coolify#7216
• coollabsio/coolify#6294
• coollabsio/coolify#5486
• coollabsio/coolify#5768
• coollabsio/coolify#6451
• coollabsio/coolify#6178
• coollabsio/coolify#6635
• coollabsio/coolify#5595

🔗 Related PRs

#6689 - v4.0.0-beta.430 [merged] | .github/workflows/chore-pr-comments.yml:
"""

AI-generated summary of changes

Adds a GitHub Actions workflow at .github/workflows/chore-pr-comments.yml that triggers on PRs when labeled. Introduces a job "add-comment" with ubuntu-latest, PR write permissions, and a matrix-based mapping of two labels to corresponding comment bodies. For each labeled PR, it posts a tailored comment to the PR using the gh CLI, gated by a conditional that checks the event label against the matrix entry. Includes environment variables for token, repo, PR number, and body, and supports an additional commented-out enhancement path. Provides specific guidance messages for labels "⚙️ Service" and "🛠️ Feature" and references to Coolify documentation contribution URLs.

Alterations to the declarations of exported or public entities

• None. No exported/public entity signatures were modified.

Estimated code review effort: Medium
"""

---

config/constants.php:
"""

AI-generated summary of changes

• Bumps the Coolify beta version in the configuration from 4.0.0-beta.429 to 4.0.0-beta.430. No other behavioral changes detected in the diff.

• Method added: none

• Method signature updated: none

• Variable renamed: none

Estimated code review effort: Medium
"""

---

other/nightly/docker-compose.prod.yml:
"""

AI-generated summary of changes

• Updated the soketi service image tag from 1.0.9 to 1.0.10. This changes the exact container image used for the soketi service; no other configuration or health check logic is touched.

Alterations to the declarations of exported or public entities

• None. No exported/public entity signatures were changed.

Estimated code review effort: Low
"""

---

other/nightly/docker-compose.windows.yml:
"""

AI-generated summary of changes

Changed the soketi service image for the coolify-realtime component from 1.0.0 to 1.0.10. No other changes to service configuration, healthchecks, or dependencies.

Alterations to the declarations of exported or public entities

• No changes to exported/public declarations detected.

Estimated code review effort: Low
"""

---

other/nightly/versions.json:
"""

AI-generated summary of changes

• Bumps version strings in other/nightly/versions.json:
  • coolify.v4.version: 4.0.0-beta.428 -> 4.0.0-beta.430
  • coolify.nightly.version: 4.0.0-beta.429 -> 4.0.0-beta.431
• No other fields in the file are modified.

Alterations to the declarations of exported or public entities

• None. No exported/public declarations were modified.

Estimated code review effort: Low
"""

---

versions.json:
"""

AI-generated summary of changes

Two version fields were incremented:

• coolify.v4.version updated from "4.0.0-beta.429" to "4.0.0-beta.430"
• coolify.nightly.version updated from "4.0.0-beta.430" to "4.0.0-beta.431"

No other entries changed.

• Field modified: version in object coolify.v4 → from "4.0.0-beta.429" to "4.0.0-beta.430"
• Field modified: version in object coolify.nightly → from "4.0.0-beta.430" to "4.0.0-beta.431"

Estimated code review effort: Medium
"""

---

app/Jobs/ApplicationDeploymentJob.php:
"""

AI-generated summary of changes

In ApplicationDeploymentJob::deploy_docker_compose_buildpack, when not using Build Secrets and there are non-empty build arguments, the code now escapes single quotes in the assembled build-args string before appending it to the docker-compose build command. This changes the control flow and input handling for the build command construction, preventing Bash parsing issues with single quotes.

• No exported/public entity signatures were modified.

Estimated code review effort: Medium
"""

---

resources/views/livewire/project/shared/environment-variable/add.blade.php:
"""

AI-generated summary of changes

• Removed the combined condition ($isNixpacks) from the Blade if guard, changing the block visibility to only depend on !$shared. Previously the block showed when either !$shared or $isNixpacks; now it shows only when !$shared.
• Minor formatting adjustment inside the block: the is_runtime checkbox attributes are consolidated onto a single line, reducing line breaks but preserving functionality. No change to the label or helper texts other than inline formatting.

Alterations to the declarations of exported or public entities

• None. No signatures of exported/public entities were changed.

Estimated code review effort: Medium
"""

---

app/Livewire/Project/Application/PreviewsCompose.php:
"""

AI-generated summary of changes

• In the branch using an existing domain, extracts the port from the domain URL via getPort(), forming a string with a leading colon when present, or an empty string when absent.
• Replaces the {{port}} placeholder in the preview URL template with the computed port string.
• The rest of the URL assembly logic remains unchanged: random, domain, pr_id substitutions, and final schema-prefixed URL assembly.

Alterations to the declarations of exported or public entities

• No exported or public API declarations changed.

Estimated code review effort: Medium

Estimated code review effort: Medium
"""
#6694 - v4.0.0-beta.431 [merged] | config/constants.php:
"""

AI-generated summary of changes

• Bumps the coolify version from 4.0.0-beta.430 to 4.0.0-beta.431; no other config entries or logic altered. Control flow and error handling remain unchanged.

Estimated code review effort: Low
"""

---

docker/production/Dockerfile:
"""

AI-generated summary of changes

Adds a new step to the production Dockerfile to upgrade APK packages before installing system dependencies, shifting the installation flow to use upgraded packages first.

• None

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Medium
"""

---

other/nightly/versions.json:
"""

AI-generated summary of changes

• Updated patch versions in other/nightly/versions.json:
  • coolify.v4.version: 4.0.0-beta.430 -> 4.0.0-beta.431
  • coolify.nightly.version: 4.0.0-beta.431 -> 4.0.0-beta.432
• Other entries remain unchanged.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Low
"""

---

versions.json:
"""

AI-generated summary of changes

• Updated version strings in versions.json: coolify.v4.version changes from 4.0.0-beta.430 to 4.0.0-beta.431; coolify.nightly.version changes from 4.0.0-beta.431 to 4.0.0-beta.432. Other entries remain unchanged.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Low
"""

👤 Suggested Assignees

• andrasbacsai
• arvilmena
• Talkless
• gterminator
• ShadowArcanist

---

🧪 Issue enrichment is currently in early access.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

[christopherpickering]

Same problem here, the coolify-db contiainer dissapears and then dashboard is not accessible. I reran the installer and the containers came back. Restarting it as noted above would do the same thing.

[Cinzya]

This has been a problem for a while, it's usually the redis container not starting properly. We aren't sure what exactly causes this issue as it's not easily reproducable. For some reason the update from v4.0.0-beta.451 to v4.0.0-beta.452 triggered it a lot for people this time.
I would assume because of the migrations.

If affected people could share their update and installation logs under /data/coolify/source that could potentially help figuring out what exactly causes this.

[christopherpickering]

I went through the last few update files (not sure which one was the cause) so here are a few that had an error message:

Creating backup of existing .env file to .env-2025-12-03-06-00-23
Merging .env.production values into .env
.env file merged successfully
Checking and updating environment variables if necessary...
 Container coolify-realtime  Recreate
 Container coolify-redis  Stopping
 Container coolify-db  Stopping
 Container bfe57dc212d7_coolify-redis  Recreate
 Container 9b6d2f208f89_coolify-db  Recreate
 Container bfe57dc212d7_coolify-redis  Error response from daemon: Error when allocating new name: Conflict. The container name "/coolify-redis" is already in use by container "bfe57dc212d7ab9fdbf8ccdadfaacc28fb0689704dc53e84e160d9ab11dd48b3". You have to remove (or rename) that container to be able to reuse that name.
 Container 9b6d2f208f89_coolify-db  Error response from daemon: Error when allocating new name: Conflict. The container name "/coolify-db" is already in use by container "9b6d2f208f899cd96ccf67fec12143f74c1886fd4ee67818c15d98f365126373". You have to remove (or rename) that container to be able to reuse that name.
 Container coolify-realtime  Recreated
 Container coolify-db  Stopped
 Container coolify-db  Removing
 Container coolify-db  Removed
 Container coolify-redis  Error while Stopping
Error response from daemon: Error when allocating new name: Conflict. The container name "/coolify-db" is already in use by container "9b6d2f208f899cd96ccf67fec12143f74c1886fd4ee67818c15d98f365126373". You have to remove (or rename) that container to be able to reuse that name.
exit status 1

or

Creating backup of existing .env file to .env-2025-12-02-06-00-20
Merging .env.production values into .env
.env file merged successfully
Checking and updating environment variables if necessary...
Creating backup of existing .env file to .env-2025-12-02-06-00-20
Merging .env.production values into .env
.env file merged successfully
Checking and updating environment variables if necessary...
 Container coolify-realtime  Recreate
 Container coolify-redis  Recreate
 Container coolify-db  Recreate
 Container coolify-redis  Recreate
 Container coolify-realtime  Recreate
 Container coolify-db  Recreate
 Container coolify-db  Error response from daemon: Conflict. The container name "/9b6d2f208f89_coolify-db" is already in use by container "5257dbb408de5c5c873e4b847f1b3e6b7d570cfa9a0228ba7d515cf26b4ce195". You have to remove (or rename) that container to be able to reuse that name.
Error response from daemon: Conflict. The container name "/9b6d2f208f89_coolify-db" is already in use by container "5257dbb408de5c5c873e4b847f1b3e6b7d570cfa9a0228ba7d515cf26b4ce195". You have to remove (or rename) that container to be able to reuse that name.
exit status 1
 Container coolify-realtime  Error response from daemon: Conflict. The container name "/c6bf08f52fe7_coolify-realtime" is already in use by container "44ccfef60040229e55fb032c2d8403b19816c4e43fb7d2a415e6de3ca25c7827". You have to remove (or rename) that container to be able to reuse that name.
Error response from daemon: Conflict. The container name "/c6bf08f52fe7_coolify-realtime" is already in use by container "44ccfef60040229e55fb032c2d8403b19816c4e43fb7d2a415e6de3ca25c7827". You have to remove (or rename) that container to be able to reuse that name.
exit status 1

successful ones look like this:

Merging .env.production values into .env
.env file merged successfully
Checking and updating environment variables if necessary...
 Container coolify-db  Recreate
 Container coolify-realtime  Recreate
 Container 5c4e5f5b7c26_coolify-redis  Recreate
 Container 5c4e5f5b7c26_coolify-redis  Recreated
 Container coolify-db  Recreated
 Container coolify-realtime  Recreated
 Container coolify  Recreate
 Container coolify  Recreated
 Container coolify-redis  Starting
 Container coolify-db  Starting
 Container coolify-realtime  Starting
 Container coolify-realtime  Started
 Container coolify-db  Started
 Container coolify-redis  Started
 Container coolify-realtime  Waiting
 Container coolify-db  Waiting
 Container coolify-redis  Waiting
 Container coolify-db  Healthy
 Container coolify-realtime  Healthy
 Container coolify-redis  Healthy
 Container coolify  Starting
 Container coolify  Started
 Container coolify-realtime  Waiting
 Container coolify  Waiting
 Container coolify-db  Waiting
 Container coolify-redis  Waiting
 Container coolify-db  Healthy
 Container coolify-redis  Healthy
 Container coolify-realtime  Healthy
 Container coolify  Healthy

[djsisson]

this feels like some kind of race condition where docker hasn't release the old container names yet, before compose tries to recreate the container (note names are deterministic here, so the container name should be the same)

i mentioned this in a past thread, where you can have issues as tear down does not happen in reverse, so coolify could be trying to use the db container as youre trying to take it down etc.

imo you should just run compose down first if you want to recreate

docker compose down && docker compose up -d --remove-orphans --wait --wait-timeout 60
or even compose stop coolify, followed by compose down to prevent dependency issues

coolify/scripts/upgrade.sh

Lines 69 to 71 in a528f4c

	docker run -v /data/coolify/source:/data/coolify/source -v /var/run/docker.sock:/var/run/docker.sock ${DOCKER_CONFIG_MOUNT} --rm ${REGISTRY_URL:-ghcr.io}/coollabsio/coolify-helper:${LATEST_HELPER_VERSION} bash -c "LATEST_IMAGE=${LATEST_IMAGE} docker compose --env-file /data/coolify/source/.env -f /data/coolify/source/docker-compose.yml -f /data/coolify/source/docker-compose.prod.yml -f /data/coolify/source/docker-compose.custom.yml up -d --remove-orphans --force-recreate --wait --wait-timeout 60" >>"$LOGFILE" 2>&1
	else
	docker run -v /data/coolify/source:/data/coolify/source -v /var/run/docker.sock:/var/run/docker.sock ${DOCKER_CONFIG_MOUNT} --rm ${REGISTRY_URL:-ghcr.io}/coollabsio/coolify-helper:${LATEST_HELPER_VERSION} bash -c "LATEST_IMAGE=${LATEST_IMAGE} docker compose --env-file /data/coolify/source/.env -f /data/coolify/source/docker-compose.yml -f /data/coolify/source/docker-compose.prod.yml up -d --remove-orphans --force-recreate --wait --wait-timeout 60" >>"$LOGFILE" 2>&1

or even just compose up since i cant see a reason why you would want to recreate the db or redis containers if they haven't changed image, and let compose handle recreation only when required.

[Realalirezayazdanpanah]

had the same exact isssue on veresion v4.0.0-beta.452

[SeriousM]

If affected people could share their update and installation logs under /data/coolify/source that could potentially help figuring out what exactly causes this.

of course, here you go!

Logs.zip

A few highlights:

a lot of toomanyrequests

toomanyrequests: retry-after: 916.659µs, allowed: 44000/minute
exit status 1

missing coolify-realtime container?

# upgrade-2025-12-03-00-00-20.log
Creating backup of existing .env file to .env-2025-12-03-00-00-20
Merging .env.production values into .env
.env file merged successfully
Checking and updating environment variables if necessary...
 Container coolify-realtime  Recreate
 Container coolify-redis  Recreate
 Container coolify-db  Recreate
 Container coolify-realtime  Error response from daemon: No such container: 97de9a8d7f1bfb6b382c20b5a6287d3c58d8225a28324c44f7f1430baaea06a5
Error response from daemon: No such container: 97de9a8d7f1bfb6b382c20b5a6287d3c58d8225a28324c44f7f1430baaea06a5
exit status 1

after recreating the db container, for some reason, it got a wired prefix "a8ef7e4cd770_coolify-db". I removed and rerun the docker compose command, now the container has its normal name "coolify-db".

[djsisson]

@SeriousM due to the --force-recreate option, the containers are taken down first, but if you are rate limited or fail to pull the newer image, this can leave you in a broken state.

i notice it is running the upgrade at the exact same moment everyday, if this is the autoupdate and everyone runs at the same moment, you hit ghcr.io rate limits, this should absolutely be changed to be a random time in the day not all at the same time. as i imagine other services also do the same thing without realising.

i cant understand why compose is adding the prefix to the container name, usually this is the project or if not specified the directory which would be source, however this is invoked via a container with a mounted path, so i think it reverts to using the hostname of the helper container which is random. But container name is specified in the compose so this shouldn't happen.

there must be some quirk here with container naming conflicts, so 2 things to add

`) docker pull should be ran beofre upgrading to ensure images are present before taking down
2) -p coolify (project name) should be added to make sure the coolify helper hostname is not added as a prefix, since --force-recreate doesnt take down that container as its not named in the compose