Docker app deployment fails because the host channel is not provisioned

[pentiminax]

Summary

Deploying a Docker app fails when OpenShip itself runs in a container because the host execution channel has not been provisioned.

Error

This operation targets the HOST machine, but no host channel is configured (OPENSHIP_HOST_SSH_HOST is unset) and Openship is running in a container — so it would have run inside the container instead, against the wrong filesystem. Re-run openship up to provision the host channel.

Steps to reproduce

1. Install and run OpenShip using Docker.
2. Create a Next.js application.
3. Start its deployment.
4. The deployment fails with the error above.

Expected behavior

openship up should automatically provision and persist a working host channel for containerized installations.

Docker applications should deploy without requiring additional undocumented configuration.

Actual behavior

OPENSHIP_HOST_SSH_HOST is unset, so OpenShip cannot safely execute operations against the host filesystem. The problem is only discovered when deploying an application.

Suggested improvements

• Provision the host channel automatically during openship up.
• Validate the host channel before completing installation.
• Provide a health check for host execution.
• Document how to repair or reprovision the channel on an existing installation.
• Include a verification command in the error message.

[Hydralerne]

on it