[GH-ISSUE #349] Database restart failure #224

New issue

Closed

opened 2026-03-03 11:14:09 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 11:14:09 +03:00

Owner

Originally created by @pavanbhaskardev on GitHub (Jul 16, 2025).
Original GitHub issue: https://github.com/dflow-sh/dflow/issues/349

Originally assigned to: @pavanbhaskardev on GitHub.

After stopping a exposed database, and restarting it back again is failing

Error response from daemon: Cannot link to a non running container: /dokku.mongo.ideologica-db AS /dokku.mongo.ideologica-db.ambassador/mongo
Error: failed to start containers: dokku.mongo.ideologica-db.ambassador

When stopping a exposed database, we need to un-expose it first and stop, so during restart we won't have issue
after restart we need to expose the old ports

Originally created by @pavanbhaskardev on GitHub (Jul 16, 2025). Original GitHub issue: https://github.com/dflow-sh/dflow/issues/349 Originally assigned to: @pavanbhaskardev on GitHub. 1. After stopping a exposed database, and restarting it back again is failing ``` Error response from daemon: Cannot link to a non running container: /dokku.mongo.ideologica-db AS /dokku.mongo.ideologica-db.ambassador/mongo Error: failed to start containers: dokku.mongo.ideologica-db.ambassador ``` 2. When stopping a exposed database, we need to un-expose it first and stop, so during restart we won't have issue 3. after restart we need to expose the old ports

kerem

2026-03-03 11:14:09 +03:00

closed this issue
added the
backend

bug
labels

kerem commented

2026-03-03 11:14:10 +03:00

Author

Owner

@pavanbhaskardev commented on GitHub (Sep 22, 2025):

Restricting stop of exposed database, pushed changes to main (commit)

@pavanbhaskardev commented on GitHub (Sep 22, 2025): Restricting stop of exposed database, pushed changes to main ([commit](https://github.com/dflow-sh/dflow/commit/e1d9248c51b7fee23ee59f50af048fb8cb9f77d1))