New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker build stucks Windows Image - LTSC2019 and 2004 #295
Comments
I'll check again. |
Hmm, I've tried, but it succeeds.
Here is the software vesions. Git revision:
Windows version:
Based image:
Docker version:
Build with:
Ruby:
|
If newer msys2 was available, it may be resolved, but not released yet. 🤔 |
Hello, Did you try with a server version? I do believe the issue is related to the Server version. I tried both LTSC and 2004. |
Yes, not the server edition. |
Bringing this up again .. Anyone else faced the same issue on a Windows Server version? |
I am trying the dockerfile provided at the following but the build fails at the copy fluentd.conf step and it says @kanhys, Can you please share the dockerfile if it is working for you already or someone let me know what's happening wrong? |
You need to put |
See https://community.chocolatey.org/packages/msys2/#versionhistory It's recommended using latest msys2 to avoid build stuck. It may solve fluent#295, probably. Signed-off-by: Kentaro Hayashi <hayashi@clear-code.com>
See https://community.chocolatey.org/packages/msys2/#versionhistory It's recommended using latest msys2 to avoid build stuck. It may solve fluent#295, probably. NOTE: Using 20220118.0.0, 20220128.0.0 causes ridk install error. Signed-off-by: Kentaro Hayashi <hayashi@clear-code.com>
See https://community.chocolatey.org/packages/msys2/#versionhistory It's recommended using latest msys2 to avoid build stuck. It may solve #295, probably. NOTE: Using 20220118.0.0, 20220128.0.0 causes ridk install error. Signed-off-by: Kentaro Hayashi <hayashi@clear-code.com>
Hello,
I usually built this image without any problem on ltsc2019 and 2004 (SAC) images, however myself and collegues are getting stuck here:
I noticed an issue opened one year ago number 208 reported the same behavior. Don't know if any Windows Update might causing this as well as any ruby bug. I already tried the latest ruby version, no success. Also, something caught my attention is that the CPU utilization for the dockerd process remains around 30%~50% until manually close the process.
Docker engine version: 20.10.5
Host Windows Version: 10.0.17763 Build 17763
Base image: mcr.microsoft.com/windows/servercore:ltsc2019 (latest)
Any clue?
The text was updated successfully, but these errors were encountered: