esh-pfi-infrastructure/persistent-memory.d/2026-09-17-servers-fv-ml1-ssh-target-was-bare-10-251-50-54-so-deploy.md

[2026-09-17] servers/fv-ml1/ssh-target was bare 10.251.50.54, so deploy-stack.sh connected as lkraven and could not write the infra-ops-owned /opt/docker/compose/

servers/fv-ml1/ssh-target was bare 10.251.50.54, so deploy-stack.sh connected as lkraven and could not write the infra-ops-owned /opt/docker/compose/ — and lkraven's sudo on fv-ml1 needs a password, so DEPLOY_SUDO=1 failed too. Now infra-ops@10.251.50.54; --validate-only still clean, deploy works. ⚠ Other hosts' ssh-target files may carry the same gap — a read-only refresh works as either user, so the fault only surfaces on a deploy.