[Feature]: Allow `privileged` mode for docker on GCP

[rejuvyesh]

Problem

GCSFuse allows mounting a remote GCS bucket as a local filesystem and is a standard thing to do in HPC contexts. https://github.com/GoogleCloudPlatform/gcsfuse/issues/566 means that mounting a fuse system inside docker requires running it in privileged mode. It seems current instance configuration chooses to not allow passing in any config to docker run.

Solution

For TPU support, dstack already enables privileged mode for the docker image. We just need to allow that to happen for standard GPUs on GCP as well.

Workaround

No response

Would you like to help us implement this feature by sending a PR?

Yes

[peterschmidt85]

@rejuvyesh Could you please hardcode the privileged flag, run dstack server from sources, and see if this fixes the problem with GCSFuse?

If all works (it's is important to ensure this in advance), then we can find a way to make privileged configurable from the YAML configuration.

[peterschmidt85]

This issue is stale because it has been open for 30 days with no activity.

[rejuvyesh]

Sorry, got busy with other things. Will likely have more time after next week.

[un-def]

The privileged property is available since 0.18.18. If you still have issues with privileged: true in the run configuration, please open another issue with steps to reproduce.