Resource Saver sometimes not working

[djettah]

trafficstars

Description

I have absolutely idle docker setup (no running containers) yet Resource Saver is not activated. Sometimes it works, sometimes not, I haven't figured out what prevents it from running.

Reproduce

1. Enable Resource Saver
2. Set minumum resource saver threshold (30 seconds).
3. Wait for some minutes at least.
4. Nothing happens!

Expected behavior

Resource Saver should be activated. Sometimes it does, another times doesn't.

docker version

Client:
 Cloud integration: v1.0.35+desktop.5
 Version:           24.0.6
 API version:       1.43
 Go version:        go1.20.7
 Git commit:        ed223bc
 Built:             Mon Sep  4 12:28:49 2023
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.24.0 (122432)
 Engine:
  Version:          dev
  API version:      1.44 (minimum version 1.12)
  Go version:       go1.20.8
  Git commit:       HEAD
  Built:            Tue Sep 26 11:52:32 2023
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.6.22
  GitCommit:        8165feabfdfe38c65b599c4993d227328c231fca
 runc:
  Version:          1.1.8
  GitCommit:        v1.1.8-0-g82f18fe
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

Client:
 Version:    24.0.6
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.11.2-desktop.5
    Path:     /Users/djet/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.22.0-desktop.2
    Path:     /Users/djet/.docker/cli-plugins/docker-compose
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     /Users/djet/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.20
    Path:     /Users/djet/.docker/cli-plugins/docker-extension
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v0.1.0-beta.8
    Path:     /Users/djet/.docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /Users/djet/.docker/cli-plugins/docker-sbom
  scan: Docker Scan (Docker Inc.)
    Version:  v0.26.0
    Path:     /Users/djet/.docker/cli-plugins/docker-scan
  scout: Docker Scout (Docker Inc.)
    Version:  v1.0.7
    Path:     /Users/djet/.docker/cli-plugins/docker-scout

Server:
 Containers: 6
  Running: 0
  Paused: 0
  Stopped: 6
 Images: 26
 Server Version: dev
 Storage Driver: stargz
  driver-type: io.containerd.snapshotter.v1
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 8165feabfdfe38c65b599c4993d227328c231fca
 runc version: v1.1.8-0-g82f18fe
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.4.16-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 9
 Total Memory: 7.765GiB
 Name: docker-desktop
 ID: 9234c087-5a41-4e0e-9f47-94c145ac1e52
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: daemon is not using the default seccomp profile

Diagnostics ID

8015BE72-8310-4A21-8DE5-5A2CD7B62378/20231008193559

Additional Info

No response

[LEUNGHOTIN]

I have the same issue, my Docker Desktop version is 4.25.0 (126437) and macOS version is 12.7.1 (21G920) Diagnostics ID：3D3A3550-FF3E-48BB-9D82-44A2CF12D175/20231113100201

[ormarek]

Same issue on Docker Desktop v.4.25.2 on MacOS. I have noticed that it might have something to do with how long container was running prior to that or that mac was put to sleep with docker running. When I restart docker desktop it is working just fine, when I start and stop containers during short sessions it also works fine but when I'm going with full day sessions where I allow my laptop to go to sleep during a break this feature is no longer working

[mauritz-lovgren]

Running Docker Desktop 4.27.2 on macOS Sonoma 14.3.1 on Apple Silicon M3 Max. Installed Docker on fresh OS and then resource saver was working. After I started a few containers (through docker compose) that I have set to 'restart-always' in the docker compose file, the resource saver stopped working. Could the 'restart-always' option cause the resource saver to never trigger? After I completely removed these containers and restarted Docker Desktop, the resource saver started working again (it wasn't enough to just stop the containers in the dashboard).

[ormarek]

Running Docker Desktop 4.27.2 on macOS Sonoma 14.3.1 on Apple Silicon M3 Max. Installed Docker on fresh OS and then resource saver was working. After I started a few containers (through docker compose) that I have set to 'restart-always' in the docker compose file, the resource saver stopped working. Could the 'restart-always' option cause the resource saver to never trigger? After I completely removed these containers and restarted Docker Desktop, the resource saver started working again (it wasn't enough to just stop the containers in the dashboard).

Interesting find, I'll also try it

[ormarek]

After couple of days I think that @mauritz-lovgren is right about that, seems like this was the case, but I don't think this should be considered a solution

[luckyguy73]

no containers at all but resource saver refuses to start.

[luckyguy73]

ahhhhh, i solved it. i had run containers in intellij plugin and even though i stopped the containers and deleted it, somehow there must have been something from intellij to keep docker from running resource saver, because as soon as i closed intellij, resource saver activated again.

[mauritz-lovgren]

ahhhhh, i solved it. i had run containers in intellij plugin and even though i stopped the containers and deleted it, somehow there must have been something from intellij to keep docker from running resource saver, because as soon as i closed intellij, resource saver activated again.

Ok! So, this could actually be the Docker integration (Service) in IntelliJ that performs some introspection of the containers that somehow keeps them alive? Maybe in particular if containers (or docker compose services) are started by IntelliJ? I also use IntelliJ with the Docker plugin. I see that it regularly inspects the status of the services (and outputs logs etc)...

[osumko]

No containers are running, no "restart-always" directive, no setup to integrate docker with intellij. Although resource saver mode does not work unless I restart docker completely. Start containers - stop containers - no saver mode - restart docker - saver mode is not until start containers - then exact the same - stop container - no saver mode - restart docker - saver mode works again. The key here is that Restart from Docker menu does not help, only quit application, then start again. And the strange thing is that when containers stop, the memory usage by docker engine remains the same. While when quiting and restarting docker application it goes down to 800mb. This has been an issue for me for last year and never any update fixed that