Devpod fails to start with docker compose dev version

[Spacelocust]

What happened?
DevPod fails to start with "Process exited with status 1" error when using Docker Compose version 5.0.0-dev. The logs show "No Major.Minor.Patch elements found"

What did you expect to happen instead?
DevPod should either:

1. Gracefully handle non-standard version strings (like "dev", "alpha", "beta")
2. Show a clear error message like "Unsupported Docker Compose version format: 'dev'. Please install a stable release (2.x or later)"
3. Skip version validation if the version string is unparseable

How can we reproduce the bug? (as minimally and precisely as possible)

1. Install Docker Compose 5.0.0-dev (available in Arch Linux repos as docker-compose 5.0.0-1)
2. Verify docker compose version returns "Docker Compose version dev"
3. Create any workspace with devcontainer.json with a compose.yml
4. Run devpod up <workspace>
5. DevPod will fail with "No Major.Minor.Patch elements found" and exit status 1

My devcontainer.json:

{
    "name": "Backend",
    "dockerComposeFile": "../compose.yml",
    "service": "back",
    "workspaceFolder": "/opt/app"
}

Local Environment:

• DevPod Version: v0.6.15
• Operating System: arch-linux
• ARCH of the OS: AMD64

DevPod Provider:

• Local/remote provider: docker

Anything else we need to know?

The issue occurs because Docker Compose 5.0.0 is still in development and reports its version as "dev" instead of a semantic version. This affects Arch Linux users who may unknowingly install pre-release versions from official repos.

Workaround: Install a version of docker-compose plugin which return a version with Major.Minor.Patch like 5.0.0

Suggested fix: Update version parsing logic to handle non-semver strings gracefully or add validation with helpful error messages for unsupported versions.

[dvdscripter]

There is a MR to fix at Arch Linux side

[Spacelocust]

The MR on the Arch Linux Docker‑Compose package repository has been merged