SymLink Option needed

[devprojectsme]

          It still fails, but at least there is an error message:

For security reasons, C:\ProgramData\DockerDesktop cannot be a symlink

Is there a list of which folders can or can't be symlinks? I would rather minimize the amount of data stored on C:

Originally posted by @Xilef11 in https://github.com/docker/for-win/issues/12650#issuecomment-1116077172

The same issue here. Just still not getting the "big concept", one pays for the Docker Desktop license, but the developers provide a new version with the changes where the user has no way to opt out. CVE? Great, but why I can not decide on a particular host whether I need the symlink or not?

So instead of bloating out the size of the C drive I much rather prefer to use the mounted volume. You know of CVE - great, give me a warning and let me use the software the way I need it on the hardware I use, instead of deciding whether or not I can configure it differently and then have to change the IaaC code and reconfigure the whole set of VMs.

So now if the user wants to update his Docker Dektop, to use the newer Kubernetes Version , as the previous has EOLed will he get an option to, or just is forced to switch to the other product?

[devprojectsme]

Seems that the current option would only be to try using the different "data-root" attribute in docker config See https://github.com/docker/for-win/issues/13476#issuecomment-1542951068 Just need to make sure your WSL2 still can mount the path referenced.

[devprojectsme]

Well that has also not worked, as there is another internal setting "dataFolder" that still points to

"dataFolder":"C:\ProgramData\DockerDesktop\vm-data"

:(

[bsousaa]

can you share context of what you're trying to achieve?

[henryse]

I'm seeing the same issue.

I'm trying to upgrade Docker Desktop to a new version.

[devprojectsme]

can you share context of what you're trying to achieve?

what I am trying to achieve, is to let my C Drive intact after installing the Docker-Desktop, but have an option as previously to use the symlink for referencing the other(i.e. external/mounted drive or parttion) where all of my images/volumes would reside.

This can then be used by the admins who try to use templates with docker in it for VMs and mount external drives to them.

Otherwise, you are forced to change you IT landscape by resizing the primary partition, which itself without additional software in windows is tedious.

The option of being able as an administrator still to configure symlink is basically the main point of this request.

[tombrau]

has anyone ever gotten this to run, as I'm seeing the same issue.

I'm trying to upgrade Docker Desktop to a new version (4.32.0).

maybe a guide to get around this would be good, haven't found anything myself.