Latest update leaves GUI blank white but tool tray says running?

[localpath]

• I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• I have uploaded Diagnostics
• Diagnostics ID: 281AAD03-FB38-4863-9D4A-04A2C31F240D/20220603133658

Actual behavior

After updating to latest release (non-experimental enabled), docker desktop GUI is blank white, restarts do not help. The window is stuck in place, cannot minimize or move it, only focusing a window over it, so anything underneath in on the desktop is obscured. If you start docker desktop you can see GUI as normal until it gets past the initial load then goes into stuck blank screen once it presents your containers, I saw the update was around container table updates so this makes sense?

Expected behavior

The GUI to be interactive.

Information

• Windows Version: Windows 11 Home, v 21H2, OS build 22000.675, Windows Feature Experience Pack 1000.22000.675.0
• Docker Desktop Version: 4.9.0
• WSL2 or Hyper-V backend? WSL2
• Are you running inside a virtualized Windows e.g. on a cloud server or a VM: no

Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check

PS C:\Users\garri> & 'C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe' check
Starting diagnostics

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0031: does the Docker API work?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0001: is the application running?
[SKIP] DD0018: does the host support virtualization?
[PASS] DD0002: does the bootloader have virtualization enabled?
[PASS] DD0017: can a VM be started?
[PASS] DD0024: is WSL installed?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0005: is the user in the docker-users group?
[PASS] DD0007: is the backend responding?
[PASS] DD0014: are the backend processes running?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[PASS] DD0006: is the Docker Desktop Service responding?
[PASS] DD0012: is the VM networking working?
[PASS] DD0032: do Docker networks overlap with host IPs?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?
No fatal errors detected.

Steps to reproduce the behavior

1. Download update
2. UI is broke at container screen then locks?
3. Remove install, download newest version, installed, seems to work so far
4. Build compose file
5. Click to the container GUI -> broke and stuck again

[TheError133]

Same problem. Both on Windows 10 and Mac OS Docker Desktops. Anything is accessible except container page. Selecting the latter makes UI blank (black in my case). Closing window via task bar is working, then I can get to settings and anything else. But not to containers.
I tried to install fresh version. In that case I can get to container page. I can even see new style of it if I create new container with it open. But then on changing page or closing the UI problem returns.
UI looks like that

[flapjackfiasco]

Same exact thing on Windows 10 using Hyper-V. Every page works fine except the Containers page is blank (white, not black, in my case). Can close the open window from the system tray icon, but the whited-out container page persists.

Diagnostics ID: 5660F29D-0440-4A07-A1F3-8A4DEF934892/20220603164600

[PASS] DD0027: is there available disk space on the host?
[SKIP] DD0028: is there available VM disk space?
[PASS] DD0031: does the Docker API work?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0001: is the application running?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0002: does the bootloader have virtualization enabled?
[PASS] DD0020: is the Hyper-V Windows Feature enabled?
[PASS] DD0017: can a VM be started?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0005: is the user in the docker-users group?
[PASS] DD0007: is the backend responding?
[PASS] DD0014: are the backend processes running?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[PASS] DD0006: is the Docker Desktop Service responding?
[PASS] DD0012: is the VM networking working?
[PASS] DD0032: do Docker networks overlap with host IPs?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?
No fatal errors detected.

[TheError133]

Diagnostics ID: 2D7E8F7C-D2BF-4063-B45A-67073766B174/20220603181955

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0031: does the Docker API work?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0001: is the application running?
[SKIP] DD0018: does the host support virtualization?
[PASS] DD0002: does the bootloader have virtualization enabled?
[PASS] DD0017: can a VM be started?
[PASS] DD0024: is WSL installed?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0005: is the user in the docker-users group?
[PASS] DD0007: is the backend responding?
[PASS] DD0014: are the backend processes running?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[PASS] DD0006: is the Docker Desktop Service responding?
[PASS] DD0012: is the VM networking working?
[PASS] DD0032: do Docker networks overlap with host IPs?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?
0 failures detected

[nomuna]

It is happening on my machine only if I try to see the containers...

[Nuklon]

Same here, just blank page. Settings works if you close main window and open settings through tray.

[DingLipeng]

Same problem for Windows 11, after containers tab menu is clicked

[lomatus]

1 + for win10, same problem.

[daverhunter]

I have the same issue in Win11, present only when trying to open the containers window. The same issue was present in Ubuntu 22.04 when I tried it.
I've searched elsewhere and a similar issue happened on the Mac version due to a dialogue box not appearing correctly
Blank white dialog box put up by Docker Desktop

[lnasc256]

same problem for windows 11 and ubuntu 22.04

[lackovic]

Same problem on Windows 10, version 21H1, using Ubuntu 20.04 and 22.04.

As workaround I have downgraded to Docker Desktop 4.8.2 and suppressed upgrades until this issue will be resolved.

[bowenac]

Happens for me as well on Windows 11 with Docker Desktop 4.9.0. For now I have to just kill all containers via command and manually start a container by command. I guess that is a workaround until a fix.

[localpath]

Same problem on Windows 10, version 21H1, using Ubuntu 20.04 and 22.04.

As workaround I have downgraded to Docker Desktop 4.8.2 and suppressed upgrades until this issue will be resolved.

Same, downgraded and wiped out my dev databases 🙄

[nicks]

Thanks for the report! We're working on both a fix and on better error messaging for these kinds of UI errors.

Repro steps:

docker-compose.yml:

version: "3.9"
services:
  redis:
    image: redis
    container_name: cache

Run:

docker compose up --project-name=cache

[elegasoft]

If your Docker Desktop always comes up blank here's a temporary way to get access to all the other panels until the bug is patched:

1. Right click the Applet and choose restart Docker
2. While it's restarting double click the Applet to launch the dashboard and
3. Click on any panel other than Containers
4. When it's finished restarting you will have access to the other panels until you click on Containers or attempt to run an image from the GUI

[gjycn]

I was forced to use the console. 😭

[TheError133]

I was forced to use the console. 😭

As a temporary measure you can access your containers via VS Code with docker plugin. It provides all the main functions to work with containers.

[gjycn]

I was forced to use the console. 😭

As a temporary measure you can access your containers via VS Code with docker plugin. It provides all the main functions to work with containers.

Thank you for reminding me that there are plugins available. . Although I have this plugin, I forgot to use it. 😂

[LaurisJakobsons]

Encountered the same problem after the latest update, in my case the issue was caused by project and container having the same name.

e.g. this works, but if I change the container name to match the project name testproject UI just breaks

[gjycn]

Encountered the same problem after the latest update, in my case the issue was caused by project and container having the same name.

e.g. this works, but if I change the container name to match the project name testproject UI just breaks

I agree with you. When I just close a container without deleting it, and then modify the docker compose file to try to restart from the file (I think the new container will overwrite the old container), this bug appears. When I delete all the newly generated containers, this bug disappears. But I don't connect the two. I seem to have seen the truth, and I can happily use the container without worrying about the bug.🤣

[HighError]

+1
Windows 11
Docker Compose: https://github.com/appwrite/appwrite/blob/master/docker-compose.yml

[doodi-v1]

Encountered the same problem after the latest update, in my case the issue was caused by project and container having the same name.

e.g. this works, but if I change the container name to match the project name testproject UI just breaks

Same issue here. It is definitely related to the project name matching the container name. I had a "ubuntu" project with "ubuntu" specified as the container name. Using the cli, I performed a "docker-compose down" and all is working again in the desktop. Changing the container_name value, or removing the parameter entirely, everything still working.

[stevenlafl]

Confirming the same issue. Windows 11 21H2 (22000.708), latest Docker Desktop 4.9.0 (80466). Screencap:

[chuoke]

I think this is caused by extensions. after I disabled the extension feature, totally blank, and can't show any view.

[asiansaga]

i have no extensions (even uncheck extensions in settings) and still got blank containers tab.
Windows 11 21H2 22000.675
Docker Desktop 4.9.0 (80466)

[seamusmac]

I upgraded yesterday, same problem reported as others
Window 11, Docker 4.9.0

Containers tab > blank
tried disabling extensions cos I have none > all tabs are now blank
also tried deleting the AppData\Roaming\Docker Desktop folder, restarting etc. nothing helped

[CWKSC]

This happen when container_name same as image name

[Nuklon]

This new version also fixes blank GUI for me.

[ArcTeryX4JC]

This latest update for Windows did resolve all the issues, the only thing I had to do was in DD was cycle WSL INTERGRATION for the distros. Thanks for the quick update.

[nimalr]

Fixes the problem for me in windows 10.

[lakeshorestudios]

Hi all, thanks to useful information from @stevenlafl, we identified one possible cause of the issue. Would anyone mind install these custom builds to see if the issue still persists? We're trying to identify all possible causes for this issue
Mac Intel: https://desktop-stage.docker.com/mac/main/amd64/80969/Docker.dmg Mac M1: https://desktop-stage.docker.com/mac/main/arm64/80969/Docker.dmg Windows: https://desktop-stage.docker.com/win/main/amd64/80969/Docker%20Desktop%20Installer.exe

Thanks, solved on Mac Intel.

Hi, I installed the Build 80969 and it solved the problem on my M1 MacBook running on macOS Monterey.

[Sagittarius]

Hi all, thanks to useful information from @stevenlafl, we identified one possible cause of the issue. Would anyone mind install these custom builds to see if the issue still persists? We're trying to identify all possible causes for this issue

Mac Intel: https://desktop-stage.docker.com/mac/main/amd64/80969/Docker.dmg Mac M1: https://desktop-stage.docker.com/mac/main/arm64/80969/Docker.dmg Windows: https://desktop-stage.docker.com/win/main/amd64/80969/Docker%20Desktop%20Installer.exe

Big thanks, problem fixed on my windows 11

[nomuna]

It fixes the problem for me on Windows 10. Thank you.

[doodi-v1]

It appears this trial build solves the issue. Will we be notified on this thread when the official build is released containing this fix?

[cherrol]

Hi all, we are very sorry for the inconvenience, could you please try out these builds and send us back diagnostic ID? The purpose of the build is to debug the issue, not to resolve it yet. The blank screen is still there unfortunately for these builds, but at least diagnostics will help us have more insight on the issue

Mac Intel: https://desktop-stage.docker.com/mac/main/amd64/80967/Docker.dmg Mac M1: https://desktop-stage.docker.com/mac/main/arm64/80967/Docker.dmg Windows: https://desktop-stage.docker.com/win/main/amd64/80967/Docker%20Desktop%20Installer.exe

I tried installing this version, but it didn't fix the problem.
windows 11 22H2 (22621.105)
docker desktop 4.9.0 (80967)

Diagnostics ID: B910ABF7-A736-490F-BB47-C441783E78B1/20220616063247

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0031: does the Docker API work?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0001: is the application running?
[SKIP] DD0018: does the host support virtualization?
[PASS] DD0002: does the bootloader have virtualization enabled?
[PASS] DD0017: can a VM be started?
[PASS] DD0024: is WSL installed?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0005: is the user in the docker-users group?
[PASS] DD0007: is the backend responding?
[PASS] DD0014: are the backend processes running?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[PASS] DD0006: is the Docker Desktop Service responding?
[PASS] DD0012: is the VM networking working?
[PASS] DD0032: do Docker networks overlap with host IPs?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?
No fatal errors detected.

[sibay]

Hi all, we are very sorry for the inconvenience, could you please try out these builds and send us back diagnostic ID? The purpose of the build is to debug the issue, not to resolve it yet. The blank screen is still there unfortunately for these builds, but at least diagnostics will help us have more insight on the issue

Mac Intel: https://desktop-stage.docker.com/mac/main/amd64/80967/Docker.dmg Mac M1: https://desktop-stage.docker.com/mac/main/arm64/80967/Docker.dmg Windows: https://desktop-stage.docker.com/win/main/amd64/80967/Docker%20Desktop%20Installer.exe

Doesnt work for me. When starting docker desktop for first time after update i got GUI with
"Docker Desktop starting"
"Docker Desktop stopping"
"Docker Desktop quit"

Windows 10 Pro 21H2 Build 19044.1766

[trungutt]

@sibay That seems to be a different issue. Could you please file a separate Github issue and diagnostic ID so that we could have an eye on?

[Cajuteq]

Experienced just the same as sibay (loop of start/stop) after the patch (80969) install, never happened before, so I think the issue comes from the patch.

[EtherealLich]

Hi all, thanks to useful information from @stevenlafl, we identified one possible cause of the issue. Would anyone mind install these custom builds to see if the issue still persists? We're trying to identify all possible causes for this issue

Mac Intel: https://desktop-stage.docker.com/mac/main/amd64/80969/Docker.dmg Mac M1: https://desktop-stage.docker.com/mac/main/arm64/80969/Docker.dmg Windows: https://desktop-stage.docker.com/win/main/amd64/80969/Docker%20Desktop%20Installer.exe

Thanks, it helps. Win 11

[TromboneFreak]

Hi all, thanks to useful information from @stevenlafl, we identified one possible cause of the issue. Would anyone mind install these custom builds to see if the issue still persists? We're trying to identify all possible causes for this issue

Mac Intel: https://desktop-stage.docker.com/mac/main/amd64/80969/Docker.dmg Mac M1: https://desktop-stage.docker.com/mac/main/arm64/80969/Docker.dmg Windows: https://desktop-stage.docker.com/win/main/amd64/80969/Docker%20Desktop%20Installer.exe

Solved (Windows 10) 😄 😃

[sibay]

@sibay That seems to be a different issue. Could you please file a separate Github issue and diagnostic ID so that we could have an eye on?

Hi @trungutt ,
added a github issue. But i am sorry, no diagnostic available
#12782

[thespatt]

Fixed it for me on Windows 11 Insider build 25140

[isaidspaghetti]

macOS

Hi all, thanks to useful information from @stevenlafl, we identified one possible cause of the issue. Would anyone mind install these custom builds to see if the issue still persists? We're trying to identify all possible causes for this issue

Mac Intel: https://desktop-stage.docker.com/mac/main/amd64/80969/Docker.dmg Mac M1: https://desktop-stage.docker.com/mac/main/arm64/80969/Docker.dmg Windows: https://desktop-stage.docker.com/win/main/amd64/80969/Docker%20Desktop%20Installer.exe

---

MacOS Monterey 12.1
Diagnostics ID: A227FB47-F485-4DD1-950B-A317DD8B3528/20220616164120 (uploaded)

diagnostics.log

[nicks]

Sorry for all the trouble everyone. Today we released 4.9.1 which we've confirmed fixes the original bug. If you continue to have issues after installing v4.9.1, please file a new bug report (since it's likely you're facing a different issue).

https://docs.docker.com/desktop/release-notes/#docker-desktop-491

[bls4]

in ver 4.8 have port, but ver 4.9 port is gone, I can't see port.

[rfay]

Unfortunately, 4.9.1 doesn't run on clean Win11. Several issues including: #12784

So I haven't been able to test this.

[jpmc]

Was able to confirm that the new 4.9.1 update works for me on both Win 10 and Mac M1.

[lackovic]

4.9.1 works fine on Windows 10 21H1.

[chuoke]

Fine to windows 10 and 11

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked