37959111746
67%
develop: 67%

Ran 09 Oct 2026 04:27PM UTC

Jobs 1

Files 79

Run time 1min

Badge

Embed ▾

Committed 09 Oct 2026 04:26PM UTC coverage: 66.737%. Remained the same

Build # 37959111746

Build Type

push

github

Committed by

web-flow

Commit Message

fix(stack): recreate containers whose published host port was taken before start (#7081)

## TL;DR

stops a container service from failing to start when its published host
port is taken between create and start.

## whats broken?

containers publish with an engine-chosen host port
(`127.0.0.1::<port>`). Podman picks that port at create by opening and
closing a socket, and pasta only binds it at start. Anything that grabs
the port in between, such as an outbound connection from another stack,
fails the start with `Listen failed for HOST TCP port …: Address in
use`.

## now fixed by:

- pasta's "Address in use" is classified as a port-allocation failure,
like Docker's "port is already allocated".
- a launch that fails with a port-allocation failure removes its
container and creates a new one, which gets a new port, up to 3
attempts. The last failure is returned as before.

## ref:

- seen on: https://github.com/supabase/cli/pull/7080

Coverage Stats

4097 of 6139 relevant lines covered (66.74%)

7.37 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	37959111746.1	09 Oct 2026 04:27PM UTC	79	66.74	GitHub Action Run

supabase / cli / 37959111746
67%
develop: 67%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 37959111746

supabase / cli / 37959111746 67% develop: 67%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 37959111746

supabase / cli / 37959111746
67%
develop: 67%

README BADGES
x