Docker scout huge memory consumption
### Description After updating to the latest docker, I noticed that my system (MacBook Pro M1, 16 GB) runs out of working memory when building docker images. Checking Activity Monitor reveals a huge memory consumption by the process `docker-scout`: <img width="362" alt="Screenshot 2023-09-20 at 09 49 47" src="https://github.com/docker/for-mac/assets/2140361/fc91d27b-db82-4cf5-805e-95acf0d443e2"> This process starts shortly after the image is built, so it seems like docker-scout tries to analyse the built images. However I do not think I ever enabled docker-scout. Actually, I was not even aware about its existence. The docker scout configuration is empty, however there is clearly something in the cache: ``` % docker scout config Configuration empty. See docker scout config --help for details. % docker scout cache df ... Total: 5.0 GB ``` Other commands like `docker scout quickview` ask me for my Docker ID, which I do not have. Please, make it possible to disable docker-scout completely! ### Reproduce 1. Create a Dockerfile: ``` FROM jupyter/minimal-notebook:2023-09-18 AS test RUN touch /tmp/test ``` 2. Run `docker build -t test .` from the same directory 3. Observe the memory consumption spikes *after* the image has been built: <img width="344" alt="Screenshot 2023-09-21 at 09 51 25" src="https://github.com/docker/for-mac/assets/2140361/e2c24d40-1e7c-4229-b4ef-180f82ce45e6"> ### Expected behavior I expect that Docker should not start any new processes (or
Posted by ykazakov on Sep 21, 2023, 8:10 AM
Tags
Related issues
- [Meta] Feedback on granular control over Copilot changes
- unexpected status 401 Unauthorized issue
- [MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb
- [CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s
- Video stops playing after some minutes
- [MODEL] Claude verbose code comments by default — ignores instructions to stop.
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
github (Software)
[Meta] Feedback on granular control over Copilot changes
unexpected status 401 Unauthorized issue
[MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb
[CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s
Video stops playing after some minutes
[MODEL] Claude verbose code comments by default — ignores instructions to stop.
Scope Codex VS Code chats to the current workspace/project
Update on "Co-authored-by: Copilot" in commit messages
Docker scout huge memory consumption
### Description After updating to the latest docker, I noticed that my system (MacBook Pro M1, 16 GB) runs out of working memory when building docker images. Checking Activity Monitor reveals a huge memory consumption by the process `docker-scout`: <img width="362" alt="Screenshot 2023-09-20 at 09 49 47" src="https://github.com/docker/for-mac/assets/2140361/fc91d27b-db82-4cf5-805e-95acf0d443e2"> This process starts shortly after the image is built, so it seems like docker-scout tries to analyse the built images. However I do not think I ever enabled docker-scout. Actually, I was not even aware about its existence. The docker scout configuration is empty, however there is clearly something in the cache: ``` % docker scout config Configuration empty. See docker scout config --help for details. % docker scout cache df ... Total: 5.0 GB ``` Other commands like `docker scout quickview` ask me for my Docker ID, which I do not have. Please, make it possible to disable docker-scout completely! ### Reproduce 1. Create a Dockerfile: ``` FROM jupyter/minimal-notebook:2023-09-18 AS test RUN touch /tmp/test ``` 2. Run `docker build -t test .` from the same directory 3. Observe the memory consumption spikes *after* the image has been built: <img width="344" alt="Screenshot 2023-09-21 at 09 51 25" src="https://github.com/docker/for-mac/assets/2140361/e2c24d40-1e7c-4229-b4ef-180f82ce45e6"> ### Expected behavior I expect that Docker should not start any new processes (or
Comments (0)
No comments yet. Start the discussion.