![]() I was able to reproduce significant slow down in docker-compose execution, waiting seconds for the very first line printed on the console even to display usage on invalid command. ![]() Without any obvious explanation for super-slowness, I decided to take a risk and upgrade my own MacBook to OSX Catalina. But for some reason, I decided to take a look at it anyway and diagnose the issue. How should I prioritize this? I don’t even know if the reporter is using the latest version of the tool – the opened issue doesn’t follow the bug reporting template. Here is the story of how we solved one such report… A one-line bug reportĪn issue was reported as “docker-compose super slow on macOS Catalina” – no version, no details. And sometimes they look really weird and can result in funny investigations. ![]() Sometimes issues are very well documented, sometimes they are nothing much but some “please help” message. ![]() Photo by Caspar Camille Rubin on UnsplashĪs a Docker Compose maintainer, my daily duty is to check for newly reported issues and try to help users through misunderstanding and possible underlying bugs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
February 2023
Categories |