Repository navigation
ghostship v0.10.2
Bug fix
macOS dedicated Podman socket path — ghostship start and ghostship upgrade failed on macOS dedicated Podman machine installs introduced in v0.10.1 with statfs: no such file or directory errors.
Root cause: The v0.10.1 Linux fix for resolve_socket_path() incorrectly applied the {machine_name}/podman.sock path on macOS too. macOS dedicated machines use the in-guest socket (/run/user/<uid>/podman/podman.sock), not a host filesystem path.
Fix: Gate the Linux dedicated socket path on platform.system() == "Linux".
Upgrade: ghostship upgrade from v0.10.1 will regenerate compose.yml with the correct path.