-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When in Windows, do as Windows does. #2458
Comments
UPDATE: Oops, this is a test, not actual code. A quick glance doesn't show obviously where the problem lies. Line 26 in ad256ba
The naive solution to this problem is to just change this line to homeKey = "LOCALAPPDATA" (or APPDATA if everything currently stored is reasonable/safe to sync over the internet on logout) and I can submit a PR that changes that if desired. However, I recognize that there is probably a desire for some kind of migration process, which is a bit more complicated so I'll hold off on any such PR unless it sounds like the naive fix is acceptable.
|
It appears the source of this problem is the utilization of the |
Hello @MicahZoltu , thank you for opening this issue 👍 This modification would be non-trivial as you said, so we need to check which path of migration would be the easiest. |
Keep the following bug in mind when deciding to use the roaming or local folders: #2878 |
Sadly, it appears that rather than fixing this the problem is getting worse. Docker (or possibly Docker Desktop) is now not only creating a What would need to happen to get fixing this prioritized? As a mitigation, at least making the directory that is used configurable via environment variable or something would go a long way to mitigating this problem for those of us who care, and won't require thinking at all about migration strategies. Another simple solution that doesn't involve migration would be:
This way anyone who has an existing install with continue using |
Hi team, I am wondering if we have made any progress regarding this issue. I see a movement around the software industry to have the Also, I am very curious about which process is responsible for the creation of |
Description
In Windows, the root of the user directory (
%USERPROFILE%
) is NOT the right place to store application settings. This is a very common convention on Linux, but Windows != Linux and not all Windows users want to pretend they are running Linux. On Windows, the correct location for application settings is%APPDATA%
and the correct location for cache/large data is%LOCALAPPDATA%
or%PROGRAMDATA%
(depending on level of security consciousness).%USERPROFILE%
is the root of the user's space on the hard drive, and it is meant to hold documents that the user explicitly writes there (e.g., via a save dialog box) and to hold top-level folders for organization such asDocuments
,Videos
,Pictures
, and the appropriately hiddenAppData
folder (which is the default location where applications should be storing their data).Along with the organization problems that is caused by storing files in
%USERPROFILE%
, it also presents problems with roaming profiles and backup scripts as Windows and Windows tools do not automatically sync/backup everything in%USERPROFILE%
. For example,%APPDATA%
will be synced over the network/internet on login/logout while%LOCALAPPDATA%
will not. By storing files in the correct folders, the application is more likely to "just work" for users working in different environments.I believe that Linux actually now has a standard for environment variables similar to the Windows one, so I would encourage fixing Linux at the same time (and cease writing to
$HOME
when those are present) but I don't personally care about Linux as much. 😄 MacOS X also has a convention I believe, though I'm not sure what Docker CLI does there.Output of
docker version
:The text was updated successfully, but these errors were encountered: