⚠️ Please verify that this bug has NOT been reported before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

There was a similar issue before.

When deploying the Docker stack, the status is displayed as "Exited" because one of the containers, which is designed to run only once during startup (e.g., a migration job), is not running.

In this case, the affine_migration_job container completes its task and exits as expected, but this causes the entire stack to appear as if it is in an "Exited" state, which can be misleading.

👟 Reproduction steps

1. Deploy the Docker stack with a container that runs a one-time job (e.g., a migration task).
2. Observe the stack status after the one-time execution container finishes its task and exits.

👀 Expected behavior

The stack should show a "Healthy" or "Running" status if all other containers are running as expected, even if a one-time execution container has exited.

😓 Actual Behavior

The stack shows an "Exited" status, which might suggest an issue with the deployment, even though the behavior of the one-time execution container is correct.

Dockge Version

1.5.0

💻 Operating System and Arch

Debian GNU/Linux 12 (bookworm)

🌐 Browser

LibreWolf 138.0.4-1

🐋 Docker Version

Docker version 24.0.2

🟩 NodeJS Version

No response

📝 Relevant log output