Skip to content

Conversation

Aymendje
Copy link

@Aymendje Aymendje commented Jun 7, 2025

This should fix #806

⚠️⚠️⚠️ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/dockge/blob/master/CONTRIBUTING.md

Tick the checkbox if you understand [x]:

  • I have read and understand the pull request rules.

Description

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.
This PR adds a check to list exited containers, and verify if they exited with error code 0 (OK) or something else (NOT OK)

Fixes #(issue)
#806

Type of change

Please delete any options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • My code follows the style guidelines of this project
  • I ran ESLint and other linters for modified files
  • [] I have performed a self-review of my own code and tested it
  • I have commented my code, particularly in hard-to-understand areas
    (including JSDoc for methods)
  • My changes generate no new warnings
  • My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)

Please do not use any external image service. Instead, just paste in or drag and drop the image here, and it will be uploaded automatically.

Dracrius added a commit to Dracrius/dockge that referenced this pull request Jun 28, 2025
Merged @Aymendje's pull request that fixes the "Exited" status when container exited as expected (ie init containers)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docker Stack Shows "Exited" Status Due to One-Time Execution Container

1 participant