docker won't start! I'm stuck on "Docker Desktop stopped - docker

I've tried installing Docker and so far I've never been able to use it on my Ubuntu machine:
when I try to start Docker Desktop it only shows Docker Desktop stopped... for an indefinite amount of time. There sometimes shows up randomly an Alert with the messages "Unable to calculate image disk size" for a second or so, but it doesn't really help me at all. I'm also not Using Docker very often so I have only a little experience with it.
At this point Docker is always the first program that shows up automatically when I boot up my computer. and it instantly goes to the message: "Docker Desktop stopped..." when I click on the bug Icon I already tried the oprions "Restart", "Clean/Purge data" and "Reset to factory defaults" but none of those options helped me so far. I also can't access the Settings page it only shows a loading animation when I try to open it.

I have the same problem. The only solution I found is to reinstall docker every time I log in. It seems to work fine until I restart the computer.
It is a very bad solution but it's the best that I've got so far.

Related

Docker desktop / daemon won't start on new M1

When I try to startup Docker Desktop on a new M1Max, it gets a fatal error that the "Docker daemon failed to start". The last log item for the daemon is just a debug message "Calling HEAD /_ping".
I'd like to try to start the daemon manually on my Mac to see if there are better error details, but all of the docs for that mention using dockerd which isn't available on the Mac install.
Background: I just switched from an older MBP to a new M1Max. I replaced my Docker Desktop with the new version for Apple Silicon and everything started up fine. However, some of my containers were having issues on the new arch. While debugging those issues, I restarted Docker Desktop and began experiencing this issue. I've tried restarting my mac, but it just gives me the same error again. I've tried downgrading Docker Desktop to the last handful of older versions and still get the same message. The strange thing is that my log file for dockerd hasn't been touched since before I restarted Docker Desktop when I first encountered the error. It's like the daemon isn't even trying to start anymore. Any help would be greatly appreciated.
UPDATE: I just reset my Mac back to my starting point (after using the migration assistant to port my old MBP to the new). When I first install Docker Desktop for Apple Silicon, it starts up normally and everything runs fine. If I check on the dockerd logs, I can see it being written to. However, as soon as I restart Docker Desktop, I get the error mentioned above and dockerd stops writing to logs. Then, every time I try to start Docker Desktop, it errors with the message above.
do the following
clean uninstall docker either using brew/appcleaner
Manually install 4.5.0 M1 - https://docs.docker.com/desktop/mac/release-notes/
that is after manually installing ensure to uncheck automatic software update from setting
!! It worked for me !!

docker desktop wsl 2 backend has stopped unexpectedly

I am facing issue with Docker desktop. it is getting crashed in 15-20 min.
Docker Desktop 4.3.2
Docker 20.10.11
Windows 10 PRO
reference link: https://github.com/docker/for-win/issues/12477
I met that problem too, but that's when I start a relatively big image/container, and don't see many useful solutions on the community.
One tutorial that I follow is, add some config documents to limit the RAM use of the WSL-2, and restart my PC, it seems to work.
User Win+R, then enter '%UserProfile%' to enter the user dictionary in Windows, create a file: '.wslconfig', and then edit the file as follows:
[wsl2]
memory=8GB
swap=0
localhostForwarding=true
The 'memory' should be edited by the condition of our laptops, I used 4GB in my one. Then restart the PC.
I'm new to Docker, don't know whether it's the right solution, but it seems work in my laptop:D Hope that can help someone meet the same problem.

How do I get past the installation failure "Object reference not set to an instance of an object" for Docker Desktop 3.3.3?

I have been trying to update the version of Docker Desktop on my laptop. The latest version as of a couple of weeks ago is Docker Desktop 3.3.3. I downloaded the installer and double clicked on it to begin the installation. I confirmed execution, resulting in a window saying "Downloading package", with a heading of "Extracting installation manifest..." Then a window saying "Do you want to replace your current version of Docker Desktop 3.3.1 (63152) with this new one (64133)?" appears. After I click on "Yes", this attached error window pops up. I tried stopping and uninstalling the previous version (3.3.1), but my PC refuses to do this. I am at the end of my rope trying to get my PC to do the simplest installation. I have been working with Docker for just over a month and want to do some tutorials and labs so that I can hit the ground running once I have real work to do with it. I would appreciate any help I can get.
Had exactly the same problem as you.
You have to delete the key "Docker Desktop" and all its sub-keys, situated at "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall" in the Windows Key Registry.

Docker Desktop pull fail with "unexpected eof"

I´m facing the Problem that I can´t pull some Docker images and docker login also works just sometimes.
This occurs only under Windows 10 Pro. I also tested it under Linux and it worked with default configuration.
I´ve already searched for the solution here, but my network connection isn´t the problem, since Linux works on the same network and I also don´t use any Proxy Server which I have to configure.
I´m trying to execute docker pull postgres. The output is:
Error response from daemon: Get https://registry-1.docker.io/v2/library/postgres/manifests/latest: Get https://auth.docker.io/token?account=unkownuser&scope=repository%3Alibrary%2Fpostgres%3Apull&service=registry.docker.io: unexpected EOF
Other images fail also with the same error and sometimes even the docker login fails with the unexpected EOF error.
Everything worked fine since the last update.
I´ve already downgraded my version, but it didn´t help. I also tried to switch from windows to linux containers, no effect.
Does anybody else have this problem or did I do something wrong?
Do you use a FritzBox?
If yes try the following it helped me:
Log into your FritzBox
In the bottom left Corner is a Button called Content (I assume its called that. I got the German version which says "Inhalt")
Click "FRITZ!Box Support"
Disable Hardware acceleration

Running Docker locally in browser on Windows10: Error - IP Not Found

Ok, so here's my background first. I'm a noob in the world of commandline interfaces, but have been building websites off and on for a long time (10 yrs) using GUI's. So, I'm trying to make the switch to CLI's while also learning Docker.
Right now I'm stuck at trying to get Docker to load anything into my browser window. Here's what I've done successfully:
Installed Docker CE on my Windows 10 Machine
Setup a new virtual switch in Hyper-V Manager per these instructions and restarted the computer.
Created a new machine using this line of code docker-machine create -d hyperv --hyperv-virtual-switch "Primary Virtual Switch" manager1
Now here's where things get a little interesting. When I run the above function (I've done it twice now) it stalls on the line: Waiting for host to start...
I waited for five minutes to see if it would do anything, before killing the operation. (oh, did I mention I'm running PowerShell in Adminstrator Mode - right click on the icon to "run as administrator").
So when I re-open PowerShell to check if the new "manager1" machine has been created it comes back affirmative, but with this:
PS C:\WINDOWS\system32> docker-machine ls
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
manager1 * hyperv Running Unknown IP not found
As far as I can tell these are the steps that I need to take to get Docker to run locally in my browser window, but for the life of me, I'm lost!
Oh, I did downgrade my docker-machine version per a suggestion that I read in a git forum comment, but that was to remedy an issue with the docker-machine create command. Part of me wonders if I'm doing too much. But I honestly don't know what to do next.
UPDATE:
I don't know that this is progress, but in the Virtual Switch Manager, I did switch the external network device from the "Ethernet Connection" to the "Dual Band Wireless" option. Then I restarted my machine. Now I'm showing that the state of the machine is "Timeout". I've also started and stopped my "docker-machine manager1". It sites on the (manager1) Waiting for host to start... line for about half a minute, then proceed to the Waiting for SSH to be available... where it just sits. Here's another screen shot that captures this:
Ok, my confusion was a result of looking beyond the documentation and getting a little confused. I still don't have this fully figured out but everything I was attempting to accomplish is detailed in this getting started with Windows 10 pro article.

Resources