[GH-ISSUE #790] fails to monitor a container_name that includes a variable from .env #3571

New Issue

GiteaMirror · 2026-04-13T15:05:11-05:00

GiteaMirror commented

2026-04-13 15:05:11 -05:00

Originally created by @LunkSnee on GitHub (Aug 31, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/790

I have a set of stacks that all use the same compose.yaml template file, but with unique project variables. I've pulled this into komodo using "files on server" and it finds the compose and other files to show under "info", however the status stays as "down". Could the monitoring check evaluate the .env variable for the stack?

I set the stack's name in Komodo to "wp-abc" or whatever the ${PROJ} is for that stack.
See my compose file below.

services:
  wordpress:
    container_name: wp-${PROJ}
    image: docker.io/bitnami/wordpress:latest
    volumes:
    [...]
    environment:
    [...]
    restart: unless-stopped

and the .env includes:

### PROJECT SETTINGS
PROJ=abc
[...]

Originally created by @LunkSnee on GitHub (Aug 31, 2025). Original GitHub issue: https://github.com/moghtech/komodo/issues/790 I have a set of stacks that all use the same compose.yaml template file, but with unique project variables. I've pulled this into komodo using "files on server" and it finds the compose and other files to show under "info", however the status stays as "down". Could the monitoring check evaluate the .env variable for the stack? I set the stack's name in Komodo to "wp-abc" or whatever the ${PROJ} is for that stack. See my compose file below. ``` services: wordpress: container_name: wp-${PROJ} image: docker.io/bitnami/wordpress:latest volumes: [...] environment: [...] restart: unless-stopped ``` and the .env includes: ``` ### PROJECT SETTINGS PROJ=abc [...] ```

GiteaMirror added the seen 👀 label 2026-04-13 15:05:11 -05:00

GiteaMirror closed this issue

2026-04-13 15:05:11 -05:00

GiteaMirror commented

2026-04-13 15:05:14 -05:00

@mbecker20 commented on GitHub (Sep 1, 2025):

Komodo should handle this edge case, but this case requires container name to be extracted from "docker compose config", which only happens when Deployed with Komodo. Can you try a single Re/deploy with Komodo, and see if this fixes this issue?

@mbecker20 commented on GitHub (Sep 1, 2025): Komodo should handle this edge case, but this case requires container name to be extracted from "docker compose config", which only happens when Deployed with Komodo. Can you try a single Re/deploy with Komodo, and see if this fixes this issue?

GiteaMirror commented

2026-04-13 15:05:15 -05:00

@LunkSnee commented on GitHub (Sep 1, 2025):

yes, after redeploying, it is showing as running! I'm fine with you closing this.

@LunkSnee commented on GitHub (Sep 1, 2025): yes, after redeploying, it is showing as running! I'm fine with you closing this.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/komodo#3571