failed to remove extension "..." as it is not installed
bostick opened this issue · 8 comments
I am developing a Docker Desktop for ZeroTier and have run into a bit of trouble. Namely, I cannot uninstall the extension as it is being developed!
This is with version 4.12.0 that was just released.
Here is what I'm trying:
brenton@Brentons-M1-MacBook-Pro zerotier-docker-extension % docker extension ls
ID PROVIDER VERSION UI VM HOST
zerotier-docker-extension ZeroTier Inc. 1 tab(ZeroTier) Not started -
brenton@Brentons-M1-MacBook-Pro zerotier-docker-extension % docker extension rm zerotier-docker-extension
failed to remove extension "zerotier-docker-extension" as it is not installed
I have been able to uninstall other extensions using the same method, so I have seen that work.
Even if unsupported, please let me know where I can uninstall the extension from my machine and start over. Reinstalling Docker Desktop would be fine. I am just interested in removing this development extension through whatever means.
Here is a screenshot after clicking the Uninstall button:
Hi @bostick thanks for reporting this. It is a known issue, we have some cleanup to do... Somehow it helps to prioritize it!...
The problem is that the name of the extension is not valid. It should be something like 'zerotier/docker-extension', with a namespace (zerotier) and an image name (docker-extension).
To remove the extension you will have to do it manually:
- remove the extension folder located in '/Users/yourusername//Library/Containers/com.docker.docker/Data/extensions'
- restart Docker Desktop
Thank you! I figured it had to do with the name, but I could not figure out where to manually remove the files.
It seems that even after removing the files manually, the containers related to the zombie extensions are still started up when docker desktop is restarted.
I also ran into this. I was able to follow the recommendations above to remove the local files to get the extension removed and then I was able to install, but for some reason now, no matter what I do to update the container, it always seems to load the image that was deployed when it was installed, but wasn't. Is there an image cache for the extension VM or something?
@averche did you find a solution?
Ok found a solution for why it seemed my local was caching the zombie container after I removed the files and reinstalled everything. It seems it was actually being cached in electron so I purged the electron cache. Spent quite a bit of time debugging this, would be great if there was a way to expose this via extensions settings.