Rolled service refused for its dependency container_name #99

New issue

Closed

opened 2026-10-10 06:02:54 +00:00 by ahmad · 0 comments

ahmad commented

2026-10-10 06:02:54 +00:00

Owner

Context

deploy-vps refuses a rolled service that sets container_name. It checks with docker compose config <service>, but that command also prints the services the rolled one depends on. So a rolled api that depends on a fixed-name migrate is refused, although the api itself has no fixed name. This blocked rihla deploy run 887 (suhba/rihla#417), which failed before touching any container.

Scope

In: look for container_name only inside the rolled service's own block of the rendered config.
Out: everything else in the swap.

Acceptance criteria

Given a rolled service without container_name that depends on a service with one, when deploying, then the swap proceeds.
Given a rolled service with container_name, when deploying, then it is still refused, naming the service.

### Context deploy-vps refuses a rolled service that sets `container_name`. It checks with `docker compose config <service>`, but that command also prints the services the rolled one depends on. So a rolled api that depends on a fixed-name `migrate` is refused, although the api itself has no fixed name. This blocked rihla deploy run 887 (suhba/rihla#417), which failed before touching any container. ### Scope - In: look for `container_name` only inside the rolled service's own block of the rendered config. - Out: everything else in the swap. ### Acceptance criteria - [ ] Given a rolled service without `container_name` that depends on a service with one, when deploying, then the swap proceeds. - [ ] Given a rolled service with `container_name`, when deploying, then it is still refused, naming the service.

ahmad added the

labels

2026-10-10 06:02:54 +00:00

ahmad self-assigned this

2026-10-10 06:02:54 +00:00

ahmad referenced this issue from a pull request that will close it,

2026-10-10 06:06:40 +00:00

fix: Check container_name on the rolled service #100