Describe the bug

If I use a compose.yaml with a named volume to deploy a service with a volume, and that volume doesn't already exist, the deploy fails with an error message that doesn't explain the problem.

How to reproduce

compose.yaml

services:
  redis:
    image: redis:7-alpine
    restart: unless-stopped
    volumes:
      - redis-data:/data

volumes:
#  patreon-rss-data:
  redis-data:

$ uc deploy --recreate
Error: plan deployment: create deployment plan for service 'redis': create plan using rolling strategy: no machines available that satisfy all constraints

Expected behavior

--recreate can create services, even if they have volumes.

Environment:

• Uncloud versions:
  • Control (client) node (uc --version): The one from Support SSH CLI on machine init and add commands #173
  • Uncloud daemon (from the server) (uncloudd --version): The one from Support SSH CLI on machine init and add commands #173
• OS version (uname -a):
  • Client (control node): Linux fedora 6.17.7-200.fc42.x86_64 Great work #1 SMP PREEMPT_DYNAMIC Sun Nov 2 17:43:34 UTC 2025 x86_64 GNU/Linux
  • Server: Linux homelab-spfy-1 6.12.48+deb13-amd64 Great work #1 SMP PREEMPT_DYNAMIC Debian 6.12.48-1 (2025-09-20) x86_64 GNU/Linux

Additional context

If I remove the volumes entries, I can deploy. If I use a host path volume, I can deploy. If I do uc deploy (no --recreate), I can deploy.