Fails when container isn't installed in hardcoded path

[jacksenk]

Container-Compose/Sources/Container-Compose/Commands/ComposeUp.swift

Line 777 in 2417b8f

"PATH": "/usr/local/bin:/opt/homebrew/bin:/usr/bin:/bin:/usr/sbin:/sbin"

For Apple Container installations using Nix, the hardcoded path variable in the referenced line above results in an error "env: container: No such file or directory"

This is because container is installed at /run/current-system/sw/bin/container

Please update this file to use the user's path variable instead of hardcoding

[Cyb3rDudu]

Confirmed. But the root cause is that streamCommand overwrites your PATH with a hardcoded string ({ _, new in new } merge at ComposeUp.swift:770), not a single hardcoded binary path. Only the streamed container run is affected; the SDK-backed down/ls/IP lookups aren't. Fix is to merge your PATH in (with the standard dirs kept as a fallback so Homebrew-under-minimal-PATH still works) rather than replacing it. PR welcome.

[mvanhorn]

Implemented in #123 - streamCommand now preserves the inherited $PATH and only appends the standard fallback dirs that are missing, so container installs outside Homebrew/system paths (e.g. Nix) resolve.