Originally created by @Chloe-ko on GitHub (Nov 14, 2024).
Hi there,
one thing I'm missing after migrating from Portainer is seeing when a container is running, but it's Health-Status is still at "starting".
This matters because e.g. reverse proxies that are configured via docker labels like Caddy and Traefik only read from Docker labels once a container is fully started. This means getting past the "starting" state.
It can be really confusing seeing a Container be "running" in Komodo, then trying to access it only to get greeted by an Error 404.
Here's an example:
I user paperless-ngx, whose main container stays in the "starting" state for a good while until it changes to being running and healthy.
Checking it's status with docker inspect <container>, I get this Info:
At the same time, Komodo already shows the container as "RUNNING", which is not technically wrong, but also not entirely accurate and can get really confusing at those times where this matters.
Other people I've gotten to migrate from Portainer to Komodo have mentioned the same issue, so I know it's not just me that's missing this :p
If it would be possible it'd be great to have an extra "State" added in Komodo for containers that shows they are running, but still starting up.
Originally created by @Chloe-ko on GitHub (Nov 14, 2024).
Hi there,
one thing I'm missing after migrating from Portainer is seeing when a container is running, but it's Health-Status is still at "starting".
This matters because e.g. reverse proxies that are configured via docker labels like Caddy and Traefik only read from Docker labels once a container is _fully_ started. This means getting past the "starting" state.
It can be really confusing seeing a Container be "running" in Komodo, then trying to access it only to get greeted by an Error 404.
Here's an example:
I user paperless-ngx, whose main container stays in the "starting" state for a good while until it changes to being running and healthy.
Checking it's status with `docker inspect <container>`, I get this Info:
```
"State": {
"Status": "running",
"Running": true,
"Paused": false,
"Restarting": false,
"OOMKilled": false,
"Dead": false,
"Pid": 87554,
"ExitCode": 0,
"Error": "",
"StartedAt": "2024-11-14T09:21:53.253931246Z",
"FinishedAt": "0001-01-01T00:00:00Z",
"Health": {
"Status": "starting",
...
```
Mind the last line, **"Status": "starting",**
At the same time, Komodo already shows the container as "RUNNING", which is _not technically wrong_, but also not entirely accurate and can get really confusing at those times where this matters.
Other people I've gotten to migrate from Portainer to Komodo have mentioned the same issue, so I know it's not just me that's missing this :p
If it would be possible it'd be great to have an extra "State" added in Komodo for containers that shows they are running, but still starting up.
Thanks for the feedback! Yes it makes sense to communicate the health status when it is available, I can take a look.
@mbecker20 commented on GitHub (Nov 15, 2024):
Thanks for the feedback! Yes it makes sense to communicate the health status when it is available, I can take a look.
Just wanted to add to the above, that it would be nice to distinguish "Running" and "Healthy", as Portainer does.
@Dinth commented on GitHub (Apr 30, 2025):
Just wanted to add to the above, that it would be nice to distinguish "Running" and "Healthy", as Portainer does.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Chloe-ko on GitHub (Nov 14, 2024).
Hi there,
one thing I'm missing after migrating from Portainer is seeing when a container is running, but it's Health-Status is still at "starting".
This matters because e.g. reverse proxies that are configured via docker labels like Caddy and Traefik only read from Docker labels once a container is fully started. This means getting past the "starting" state.
It can be really confusing seeing a Container be "running" in Komodo, then trying to access it only to get greeted by an Error 404.
Here's an example:
I user paperless-ngx, whose main container stays in the "starting" state for a good while until it changes to being running and healthy.
Checking it's status with
docker inspect <container>, I get this Info:Mind the last line, "Status": "starting",
At the same time, Komodo already shows the container as "RUNNING", which is not technically wrong, but also not entirely accurate and can get really confusing at those times where this matters.
Other people I've gotten to migrate from Portainer to Komodo have mentioned the same issue, so I know it's not just me that's missing this :p
If it would be possible it'd be great to have an extra "State" added in Komodo for containers that shows they are running, but still starting up.
@mbecker20 commented on GitHub (Nov 15, 2024):
Thanks for the feedback! Yes it makes sense to communicate the health status when it is available, I can take a look.
@Dinth commented on GitHub (Apr 30, 2025):
Just wanted to add to the above, that it would be nice to distinguish "Running" and "Healthy", as Portainer does.