[Bug]: Cannot run Hugging Face Spaces docker images

[jvstme]

Steps to reproduce

> cat .dstack.yml
type: dev-environment
image: registry.hf.space/skalskip-florence-sam:latest
ide: vscode

> dstack apply --spot

Actual behaviour

 #  BACKEND  REGION      INSTANCE   RESOURCES                    SPOT  PRICE     
 1  aws      us-east-1   m5.xlarge  4xCPU, 16GB, 100.0GB (disk)  yes   $0.0544   
 2  aws      us-west-2   m5.xlarge  4xCPU, 16GB, 100.0GB (disk)  yes   $0.0582   
 3  aws      eu-north-1  m5.xlarge  4xCPU, 16GB, 100.0GB (disk)  yes   $0.0607   
    ...                                                                          
 Shown 3 of 368 offers, $41.0261 max

Submit a new run? [y/n]: y
big-wolverine-1 provisioning completed (terminating)
Cannot create container.
Error: createContainer error: Error response from daemon: No such image: 
registry.hf.space/skalskip-florence-sam:latest
Check CLI and server logs for more details.

Expected behaviour

The dev environment is launched successfully.

dstack version

master

Server logs

No response

Additional information

Hugging Face Spaces docker images use zstd for layer compression. dstack images for VM-based backends use docker 20.10.17 that does not support zstd.

[jvstme]

Hugging Face Spaces docker images will work in dstack 0.18.10 on AWS, Azure, GCP, OCI, and on-premises. The status for other backends is being clarified.

[jvstme]

Update: as of dstack 0.18.10, Hugging Face Spaces images work on all backends except Kubernetes (will work in dstack 0.18.11), RunPod and Vast.ai (will likely work once #1535 is done)