Open ambhaiji opened 2 months ago
Hi @ambhaiji,
can you please share a few more details of what you have exactly done when trying to make docker desktop play nicely with podman desktop and/or deleting the wsl-swap?
What is the behaviour you see when you start docker desktop as opposed to the behavior you were expecting?
For what I can see:
docker-desktop-data
distribution registered in WSL. Docker Desktop never deletes it, except in two cases: (1) the factory reset button is pushed or (2) docker desktop is uninstalled (3) the user manually does wsl --unregister docker-desktop-data
.
docker-desktop-data
distribution (which possibly held your previous data), Docker Desktop switched to the "mono distribution" architecture, which no longer uses a second WSL distribution for storing data, but a plain virtual hard disk (VHDX) on your file system.If you have a backup of your original data distribution it may be still easy to recover your data, if that's the issue you are facing.
(1) the factory reset button is pushed or (2) docker desktop is uninstalled
Yes I did do a restore factory defaults. It seemed like the only option given it would not run while Podman was open and I didn't know the cause at the time. Can you please help me understand a good reason to wipe volumes and images initiating factory default? I don't see any reason. I am also somewhat sure the warning was not clear enough this would happen, or I just assumed some type of default in my head.
Hey,
I am really sorry about that.
The current "factory reset" workflow does have a message that says that it would destroy all containers and images, but I take the feedback that the UI could be more aggressive in highlighting the consequences of the action.
Factory reset is intended to bring back Docker Desktop at the same stage it would be after a fresh install. For this reason it includes wiping all the content that did not come "from the factory".
Because I am unable to recreate the Podman Docker collision I am unable to check what warning I saw and as such I also do have a suggestion,
If the Reset dialoague is the same as above after this error "Something went wrong. Starting services: initializing Docker API Proxy: open .\pipe\docker_engine: Access is denied." I have the options "quit", "diagnose & feedback", and "reset Docker to factory settings."
I have suggestion to improve it to account for the seriousness of the action about to take place:
A factory reset does the following:
●Destroys all Docker containers
●Destroys all images local to the machine
●Restores the application to its original state, as when it was first installed.
Type your password below to proceed.
<text field>
Your message came in just as I was typing this one up
I also just noticed the warning does not mention the removal of volumes
Thanks for the clarification.
You're right: in case of the recovery dialog below there's no explicit mention on the fact that factory resets deletes all the user data. I agree Docker Desktop should be much more clear about that in this specific workflow - thanks for pointing that out.
must be fate then, this might be my most useful contribution to open source so far, have got to start somewhere I guess.
Can you please help me understand a good reason to wipe volumes and images initiating factory default? I don't see any reason
I was hoping I could get response to this please so I can understand more about how software system should or is expected to work. or if such such drastic measures are not fully necessary maybe can we get tick boxes or options flow to reset different parts of docker as with my case where I wanted all the settings to be default of the Docker core system and not really anything I had within it.
@ambhaiji: I believe wiping out all data is standard practice for factory reset (think, for example, at modern phones). The intention is to put back the system at the initial system conditions.
As said, we are taking your feedback very seriously and we are working on a better UX around factory reset, warning users about the implications more clearly and explicitly.
@andrea-reale yes but all modern systems have options to reset all settings without touching data. Windows itself allows you to reinstall windows while "your apps, files and settings will be preserved". The key benefits of containerizations is that since everything is segregated we can reset parts of the system in pieces to debug in a sense what needed to be reset to get things working again.
As said, we are taking your feedback very seriously and we are working on a better UX around factory reset, warning users about the implications more clearly and explicitly.
I would be happy to be a part of this discussion if you would like me to.
Similarly, this error message does not alert the user that a factory reset will delete all data.
It was triggered by a windows update and was resolved by running wsl --update --pre-release
.
Unaware of the consequences, I tried factory resetting. This deleted data that I thought was saved to an external location, was not. And was months of important collected data which cannot be recreated. I think by nature of the windows update, my windows restoration point is also no longer available which could have recovered most of the data.
Description
I tried to get rid of my wsl-swap virtual disk forcefully, in an effort to gain back some space on my drive. This all happened while I tried to get Podman Desktop to play nice with Docker Desktop, while also being in a time where Docker 4.31.x may have had issues for some people.
Extra info that may be relevant I am now running 154084 dev build Distro: Ubuntu-24.04 Podman Desktop is uninstalled
Reproduce
Unknown
Expected behavior
Removing wsl-swap while docker is shutdown should not ruin Docker in any way Removing Podman Desktop should not affect Docker in any way
docker version
docker info
Diagnostics ID
C014D5F5-FFBB-44CF-BE2F-1AB4538C1912/20240613173527
Additional Info
I am now running 154084 dev build Distro: Ubuntu-24.04 Podman Desktop is uninstalled
any help on this matter is greatly appreciated, in the meantime I'm trying to recover the disk files using recovery tools.