Skip to content

Docker paused will not resume after a while #6058

Closed
Closed
Docker paused will not resume after a while#6058
Labels
version/4.12.0version/4.16.1version/4.2.0version/4.4.2version/4.7.1version/4.8.1

Description

@jmaitrehenry
jmaitrehenry
opened on Nov 23, 2021
  • I have tried with the latest version of Docker Desktop
  • [?] I have tried disabling enabled experimental features
  • I have uploaded Diagnostics
  • Diagnostics ID: 2AC72C0C-F9FC-44D3-A6DA-E1D42B3DC250/20211123144429 and 2AC72C0C-F9FC-44D3-A6DA-E1D42B3DC250/20211122202700

Expected behavior

Docker resume when I run a docker command or by clicking resume in the menu

Actual behavior

Docker is paused:

[FAIL] DD0016: is the LinuxKit VM running? vm is not running: vm has not started

[PASS] DD0001: is the application running?
[PASS] DD0018: does the host support virtualization?
[FAIL] DD0017: can a VM be started? vm has not started: vm has not started

Information

  • macOS Version: 12.0.1 (21A559)
  • Intel chip or Apple chip: Apple M1 Pro
  • Docker Desktop Version: 4.2.0 (70708)

Steps to reproduce the behavior

  1. Pause docker
  2. Put the Mac in sleep (closing the screen of the MBP)
  3. Run a docker compose command, docker info command, try to resume by clicking Resume on the dock icon

Interesting finding in the logs:

 2021-11-22 15:09:54.675764-0500  localhost com.docker.driver.amd64-linux[10450]: Resuming vm, user agent is: Docker-Client/20.10.10 (darwin)
2021-11-22 15:09:54.677543-0500  localhost com.docker.driver.amd64-linux[10450]: (6e2a1d6d) d221324c-DriverCMD C->S BackendAPI POST /unpause
2021-11-22 15:09:54.679544-0500  localhost com.docker.backend[9569]: (6e2a1d6d) bf40619e-BackendAPI S<-C d221324c-DriverCMD POST /unpause[[STACK]]github.com/docker/pinata/common/pkg/backend.(*backendClient).Unpause(0x140000781f0)
	/Users/administrator/jenkins/workspace/op_desktop-build_master-merge_18/src/github.com/docker/pinata/common/pkg/backend/client.go:258 +0x60
github.com/docker/pinata/common/pkg/proxy.NewRouter.func2.1({0x102e69dd0, 0x140001b62a0}, 0x140000a0a00)
	/Users/administrator/jenkins/workspace/op_desktop-build_master-merge_18/src/github.com/docker/pinata/common/pkg/proxy/proxy.go:112 +0x3a4
github.com/docker/pinata/common/pkg/proxy.NewRouter.func1.1({0x102e69dd0, 0x140001b62a0}, 0x140000a0a00)
	/Users/administrator/jenkins/workspace/op_desktop-build_master-merge_18/src/github.com/docker/pinata/common/pkg/proxy/proxy.go:76 +0x184
github.com/docker/pinata/common/pkg/proxy.(*restrictions).Middleware.func1({0x102e69dd0, 0x140001b62a0}, 0x140000a0a00)
	/Users/administrator/jenkins/workspace/op_desktop-build_master-merge_18/src/github.com/doc<decode: missing data>
2021-11-22 15:09:54.679573-0500  localhost com.docker.backend[9569]: [...] ker/pinata/common/pkg/proxy/restrictions.go:74 +0x180
github.com/docker/pinata/common/pkg/proxy.(*GuiAnalytics).Middleware.func1({0x102e69dd0, 0x140001b62a0}, 0x140000a0a00)
	/Users/administrator/jenkins/workspace/op_desktop-build_master-merge_18/src/github.com/docker/pinata/common/pkg/proxy/analytics.go:62 +0xe0
github.com/gorilla/mux.(*Router).ServeHTTP(0x140001ec6c0, {0x102e69dd0, 0x140001b62a0}, 0x140000a0800)
	/Users/administrator/jenkins/workspace/op_desktop-build_master-merge_18/src/github.com/docker/pinata/vendor/github.com/gorilla/mux/mux.go:210 +0x1e4
2021-11-22 15:09:54.680238-0500  localhost com.docker.backend[9569]: (6e2a1d6d-1) e4b36909-PauseHDL C->S procd POST /unpause
2021-11-22 15:09:54.681068-0500  localhost com.docker.backend[9569]: (6e2a1d6d-1) e4b36909-PauseHDL C<-S NoResponse POST /unpause (809.583µs): Post "http://ipc/unpause": dial unix procd.sock: connect: connection refused

Activity

  1. Imagedocker-robott
    added
    version/4.2.0
    on Nov 23, 2021

  2. StefanScherer commented on Nov 24, 2021

    @StefanScherer
    StefanScherer
    on Nov 24, 2021
    Member

    Thanks for the report and for trying the new experimental feature. We're looking into it.

  3. SpadarShut commented on Dec 16, 2021

    @SpadarShut
    SpadarShut
    on Dec 16, 2021

    Same issue with with Mac Intel chip.

  4. mat007 commented on Jan 14, 2022

    @mat007
    mat007
    on Jan 14, 2022
    Member

    We have now fixed this issue in Docker Desktop 4.4.2, thank you!

  5. Imagemat007
    closed this as completedon Jan 14, 2022

  6. ppastur commented on Jan 18, 2022

    @ppastur
    ppastur
    on Jan 18, 2022

    We have now fixed this issue in Docker Desktop 4.4.2, thank you!

    I may have missed something but I have version Docker Desktop 4.4.2 (73305) and still have the problem.

  7. mat007 commented on Jan 18, 2022

    @mat007
    mat007
    on Jan 18, 2022
    Member

    @ppastur can you upload diagnostics so that we can have a look?

  8. ppastur commented on Jan 18, 2022

    @ppastur
    ppastur
    on Jan 18, 2022

    Hi @mat007 , I just tried to reproduce the error (after it happened twice my morning) and it seems to be behaving. Ill keep an eye on it and if it happens again ill grab diags and upload.

  9. SpadarShut commented on Jan 19, 2022

    @SpadarShut
    SpadarShut
    on Jan 19, 2022

    I'm still having this issue in 4.4.2. Here's my diagnostics id 10DB2225-494C-4A4E-92BA-7106942338B3/20220119102459

  10. Imagedocker-robott
    added
    version/4.4.2
    on Jan 19, 2022

  11. ebriney commented on Jan 20, 2022

    @ebriney
    ebriney
    on Jan 20, 2022
    Member

    I can reproduce it, hope to do a fix!

  12. Imageebriney
    reopened this on Jan 20, 2022

  13. mvhayman-afs commented on Feb 15, 2022

    @mvhayman-afs
    mvhayman-afs
    on Feb 15, 2022

    Also having this issue. When selecting the restart option within docker desktop it goes into a loop. Diagnosing also just seems to say 'Diagnosing...' for a long time so I can't give you a diagnostic id unfortunately.

  14. NReilingh commented on Mar 2, 2022

    @NReilingh
    NReilingh
    on Mar 2, 2022

    I'm having this issue on Apple Silicon.

    I think a compounding issue that needs fixing is that within the dashboard window, the interaction loop for clicking significant buttons like "restart and update" or "resume" has no immediate UI feedback. They seem to expect a command to return from the daemon or something before showing any visual feedback, and I suspect may even allow multiple commands to be dispatched asynchronously which can cause unexpected behavior. When a button like this is clicked, the UI needs to respond immediately by disabling further clicks of the button and showing a visual indicator that something is happening (or at least being attempted).

  15. owenduncansnobel commented on Mar 8, 2022

    @owenduncansnobel
    owenduncansnobel
    on Mar 8, 2022

    Ya I am having this issue on Apple Silicon

  16. 66 remaining items

  17. eosmantis commented on Feb 10, 2023

    @eosmantis
    eosmantis
    on Feb 10, 2023

    The issue (Docker paused and will not resume) is still reproducible Version in Docker Desktop Version 4.16.2 (95914) on MacOS Ventura 13.0

  18. eosmantis commented on Feb 10, 2023

    @eosmantis
    eosmantis
    on Feb 10, 2023

    Error-Message: "Unable to calculate image disk size" (but not visible by using the mini-menu)

  19. lprimak commented on Mar 4, 2023

    @lprimak
    lprimak
    on Mar 4, 2023

    Maybe fixed again?
    Surviving through multiple pauses for 3 days now... fingers crossed!
    version 4.17.0 (99724)

  20. alishaevn commented on Apr 5, 2023

    @alishaevn
    alishaevn
    on Apr 5, 2023

    Apple Macbook Pro 2020
    Docker 4.15.0 (93002)
    macOS 13.2.1

    I paused docker last night. Upon waking the OS from sleep this morning, I was unable to get Docker to resume by pressing "resume" from the Docker icon drop down nor the Docker dashboard. Running a docker command from the terminal hung without any messages. Restarting Docker didn't do anything, so I tried restarting a second time. The second time....it froze me out from any options from the icon drop down at all. The Docker app icon still showed the containers going up and down as though something was happening, but nothing appeared to be.

    Force closing Docker from Activity Monitor and then restarting the app is what eventually worked.

  21. lprimak commented on Apr 5, 2023

    @lprimak
    lprimak
    on Apr 5, 2023

    @alishaevn this looks fixed with the latest version you are running an older version where this is still broken.

  22. morganestes commented on Apr 11, 2023

    @morganestes
    morganestes
    on Apr 11, 2023

    @lprimak I'm on 4.17.0 and running into the problem just this morning. Can't resume or restart, and got the same "Unable to calculate image disk size" error message as @eosmantis.

  23. infoman commented on May 16, 2023

    @infoman
    infoman
    on May 16, 2023

    I'm having the opposite problem, I pause the engine and after a while it silently un-pauses itself without any commands or other obvious interaction

  24. lprimak commented on May 16, 2023

    @lprimak
    lprimak
    on May 16, 2023

    Yup. Me too. Latest update broke pause on the opposite way

  25. NotTimIsReal commented on May 16, 2023

    @NotTimIsReal
    NotTimIsReal
    on May 16, 2023 via email

  26. simonberger commented on May 31, 2023

    @simonberger
    simonberger
    on May 31, 2023

    I also have the problem of auto resuming docker engine which is annoying, especially when using in battery mode and not needing docker for a while.
    Auto resuming is not just rarely happening but at least after like 15-30min so I end up having it not paused a long time which hurts battery runtime a lot. I couldn't yet really find out why this is happening. In logs could just see the same of the initial posting

    standard	17:03:24.311490+0200	com.docker.backend	HTTP 82 CONNECT desktop.docker.com:443: with direct connection
standard	17:03:24.311490+0200	com.docker.backend	HTTP 83 CONNECT desktop.docker.com:443: with direct connection
standard	17:03:24.311500+0200	com.docker.backend	HTTP 84 CONNECT desktop.docker.com:443: with direct connection
standard	17:03:24.312158+0200	com.docker.backend	HTTP 85 CONNECT desktop.docker.com:443: with direct connection
standard	17:03:24.473253+0200	com.docker.backend	HTTP 84 CONNECT desktop.docker.com:443: 200 OK
standard	17:03:24.473423+0200	com.docker.backend	HTTP 84 CONNECT desktop.docker.com:443: proxying to desktop.docker.com:443
standard	17:03:24.513351+0200	com.docker.backend	HTTP 85 CONNECT desktop.docker.com:443: 200 OK
standard	17:03:24.513566+0200	com.docker.backend	HTTP 85 CONNECT desktop.docker.com:443: proxying to desktop.docker.com:443
standard	17:03:24.543088+0200	com.docker.backend	HTTP 82 CONNECT desktop.docker.com:443: 200 OK
standard	17:03:24.543078+0200	com.docker.backend	HTTP 83 CONNECT desktop.docker.com:443: 200 OK
standard	17:03:24.543257+0200	com.docker.backend	HTTP 82 CONNECT desktop.docker.com:443: proxying to desktop.docker.com:443
standard	17:03:24.543312+0200	com.docker.backend	HTTP 83 CONNECT desktop.docker.com:443: proxying to desktop.docker.com:443
standard	17:03:24.799576+0200	com.docker.backend	HTTP 83 CONNECT desktop.docker.com:443: successful (7 active requests)
standard	17:03:24.827802+0200	com.docker.backend	HTTP 82 CONNECT desktop.docker.com:443: successful (6 active requests)
standard	17:03:25.378329+0200	com.docker.backend	dropping ICMP 77.220.243.252 -> VM type 1 *icmp.DstUnreach
standard	17:03:25.378453+0200	com.docker.backend	dropping ICMP 77.220.243.252 -> VM type 1 *icmp.DstUnreach
standard	17:03:25.378530+0200	com.docker.backend	dropping ICMP 77.220.243.252 -> VM type 1 *icmp.DstUnreach
standard	17:03:25.496726+0200	com.docker.backend	dropping ICMP 77.220.243.252 -> VM type 1 *icmp.DstUnreach
standard	17:03:25.598625+0200	com.docker.backend	Resuming vm, user agent is: Go-http-client/1.1
standard	17:03:25.598804+0200	com.docker.backend	(2c0504e6) 040f623e-DriverCMD C->S BackendAPI POST /unpause
standard	17:03:25.599596+0200	com.docker.backend	(2c0504e6) d7f45bfe-BackendAPI S<-C 040f623e-DriverCMD POST /unpause
standard	17:03:25.618005+0200	com.docker.backend	(2c0504e6-1) 3f4fe8e5-PauseHDL C->S procd POST /unpause
standard	17:03:25.624882+0200	com.docker.backend	3f4fe8e5-PauseHDL /pause/events <-- [2023-05-31T17:03:25.654382339+02:00] (17eb0198) pause resuming : Docker Desktop is resuming...
standard	17:03:25.769934+0200	com.docker.backend	error copying: write unix <HOME>/Library/Containers/com.docker.docker/Data/lifecycle-server.sock->: write: broken pipe
standard	17:03:25.770113+0200	com.docker.backend	error copying: write unix <HOME>/Library/Containers/com.docker.docker/Data/lifecycle-server.sock->: write: broken pipe
standard	17:03:25.770320+0200	com.docker.backend	error copying: write unix <HOME>/Library/Containers/com.docker.docker/Data/lifecycle-server.sock->: write: broken pipe
standard	17:03:25.771280+0200	com.docker.backend	(cca3d18a) b85ec40c-VMDiskUsageClient C<-S 1e305d46-VMDockerdAPI GET /vm/disk-usage (4m19.123526841s): {"availableBytes":15685668864,"totalBytes":101129359360,"usedBytes":80273006592}
standard	17:03:25.771462+0200	com.docker.backend	(205efe8c) b85ec40c-VMDiskUsageClient C->S VMDockerdAPI GET /vm/disk-usage

    I am on newest version 4.20 and as described the same behavior happens to me since many versions (it was never different)

  27. ravi-rafay commented on May 14, 2024

    @ravi-rafay
    ravi-rafay
    on May 14, 2024

    Still facing this issue on docker desktop for mac v4.30.0

  28. m0n9oose commented on May 14, 2024

    @m0n9oose
    m0n9oose
    on May 14, 2024

    Fixed the problem by removing DD, and switching to an alternative app 👍

  29. hoschi commented on Jun 21, 2025

    @hoschi
    hoschi
    on Jun 21, 2025

    I have also the problem that DD doesn't resume.

  30. lprimak commented on Feb 1, 2026

    @lprimak
    lprimak
    on Feb 1, 2026

    I think this has been fixed now

  31. Imagebsousaa
    closed this as completedon Feb 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    version/4.12.0version/4.16.1version/4.2.0version/4.4.2version/4.7.1version/4.8.1

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions