Bug: no chart generated when using depends_on #182

New Issue

2026-01-19T09:08:44Z

macier-pro commented

2026-01-19 09:08:44 +00:00

Consider the following compose.yml :

services:
  svc1:
    image: alpine

  svc2:
    image: alpine
    depends_on:
      - svc1

Logs :

 katenary convert

🔵 Adding dependency from svc2 to svc1
❕ No ports found for service svc1. You should declare a port in the service or use katenary.v3/ports label.

No error message or details, and no chart output.

Removing depends_on creates the chart.

services:
  svc1:
    image: alpine

  svc2:
    image: alpine

Consider the following compose.yml : ```yaml services: svc1: image: alpine svc2: image: alpine depends_on: - svc1 ``` Logs : ```yml katenary convert 🔵 Adding dependency from svc2 to svc1 ❕ No ports found for service svc1. You should declare a port in the service or use katenary.v3/ports label. ``` No error message or details, and no chart output. Removing `depends_on` creates the chart. ```yaml services: svc1: image: alpine svc2: image: alpine ```

macier-pro changed title from ~~Bug: no chat generated when using depends_on~~ to Bug: no chart generated when using depends_on

2026-01-19 09:08:49 +00:00

metal3d commented

2026-01-19 10:53:54 +00:00

Yes that's because you need to define a port where the "initContainer" could test the service is up.
You can use the label "ports" if you don't want to expose a port from the compose file.

Yes that's because you need to define a port where the "initContainer" could test the service is up. You can use the label "ports" if you don't want to expose a port from the compose file.

metal3d referenced this issue from a commit

2026-03-08 21:52:28 +00:00

fix(err): No port with depends_on

metal3d closed this issue

2026-03-08 21:52:28 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Katenary/katenary#182