Add option to use container volumes on git-repositories

[haakobja]

Is your feature request related to a problem? I've been using DevPod for some time now, first as a Mac user and now, recently as a Windows user. Currently I'm using Podman Desktop and when programming I use the Jetbrains suite, but the Jetbrains software complains about the filesystem and notifies me that I might be using a network disk.

I realize that DevPod mounts a local file system directory, even if I didn't open that directory as a devpod. Lately, I've been using devcontainers and feed devpod with the repository ssh-url.

Which solution do you suggest?
Make an opt in feature to use container volumes for devcontainer workspaces.

Which alternative solutions exist?
I'm not aware of other solutions to this, as currently, the container runs in WSL.

Additional context
Podman containers on Windows runs in an WSL-instance. I also use KeePassXC to store SSH-keys, which is integrated with the local OpenSSH-agent instance

[bkneis]

Hi @haakobja, thanks for reporting this issue! what provider are you using?

[haakobja]

I'm using the Docker provider with the following configuration:

Please note that the podman CLI is installed and available via the $PATH environment variable

[renan-r-santos]

I'd like to add that this doesn't affect only Windows. I've been using Orbstack (Mac-only app) with named volumes, see https://docs.orbstack.dev/docker/file-sharing. When using DevPod with the Docker provider (default configuration), I see a significant file I/O performance degradation for big git repos compared to just using OrbStack with VSCode's devcontainer on a named Docker volume.

[tm-echo-arcelao]

+1 on this. Working on large git repos has been painfully slow on DevPod as the files are stored on the OS host. Any operations that involves continuous I/O such as hot reloading take significantly longer compared to VSCode Dev Containers' Docker volume binding.

[github-actions[bot]]

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

[github-actions[bot]]

This issue was closed because it has been inactive for 30 days since being marked as stale.