Skip to content
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

Open
marciogmorales opened this issue Sep 29, 2021 · 8 comments
Open

Docker build stucks Windows Image - LTSC2019 and 2004 #295

marciogmorales opened this issue Sep 29, 2021 · 8 comments
Labels
help wanted Need contributors

Comments

@marciogmorales
Copy link

marciogmorales commented Sep 29, 2021

Hello,
I usually built this image without any problem on ltsc2019 and 2004 (SAC) images, however myself and collegues are getting stuck here:

19 gems installed
Successfully installed win32-service-1.0.1
1 gem installed
Successfully installed win32-ipc-0.7.0
1 gem installed
Successfully installed win32-event-0.6.3
1 gem installed
Successfully installed windows-pr-1.2.6
1 gem installed
*** Removed specs cache ***

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?

@marciogmorales marciogmorales changed the title Docker build stucks Windows Image - LTSC2019 Docker build stucks Windows Image - LTSC2019 and 2004 Sep 29, 2021
@kenhys
Copy link
Contributor

kenhys commented Sep 30, 2021

I'll check again.

@kenhys
Copy link
Contributor

kenhys commented Sep 30, 2021

Hmm,

I've tried, but it succeeds.

[ltsc2019.txt](https://github.com/fluent/fluentd-docker-image/files/7255859/ltsc2019.txt)

Successfully installed windows-pr-1.2.6
1 gem installed
*** Removed specs cache ***
Removing intermediate container bc12d96d4e4f
 ---> c7fe6539c065
Step 7/11 : RUN powershell -Command "Remove-Item -Force C:\ruby26\lib\ruby\gems\2.6.0\cache\*.gem; Remove-Item -Recurse -Force 'C:\ProgramData\chocolatey'"
 ---> Running in 1dc732a3222b
Removing intermediate container 1dc732a3222b
 ---> 51b3d476033c
Step 8/11 : COPY fluent.conf /fluent/conf/fluent.conf
 ---> b7edc6c2cc9d
Step 9/11 : ENV FLUENTD_CONF="fluent.conf"
 ---> Running in 5b93d8d6bf2a
Removing intermediate container 5b93d8d6bf2a
 ---> bb3555f30ec2
Step 10/11 : EXPOSE 24224 5140
 ---> Running in 5a85aca0a178
Removing intermediate container 5a85aca0a178
 ---> 4c7bec41b766
Step 11/11 : ENTRYPOINT ["cmd", "/k", "fluentd", "--config", "C:\\fluent\\conf\\fluent.conf"]
 ---> Running in a1f751c33302
Removing intermediate container a1f751c33302
 ---> 120320d82638
[Warning] One or more build-args [VERSION] were not consumed
Successfully built 120320d82638
Successfully tagged fluent/fluentd:v1.14.1-windows-ltsc2019-1.0

Here is the software vesions.

Git revision:

$ git log --oneline -n 1
55c68e8 (HEAD -> master, upstream/master, origin/master, origin/HEAD) Add Fluentd v1.14.1 images

Windows version:

>ver

Microsoft Windows [Version 10.0.19043.1237]

Based image:

> docker pull mcr.microsoft.com/windows/servercore:ltsc2019
ltsc2019: Pulling from windows/servercore
Digest: sha256:2b33eda096538c803fbf0c03dc7ea42c3c1b713e30aae03116d989867eda2bf8
Status: Image is up to date for mcr.microsoft.com/windows/servercore:ltsc2019
mcr.microsoft.com/windows/servercore:ltsc2019

Docker version:

> docker --version
Docker version 20.10.8, build 3967b7d

Build with:

make DOCKERFILE=v1.14/windows-ltsc2019 VERSION=v1.14.1-windows-ltsc2019-1.0

Ruby:

 ruby -v
ruby 2.7.3p183 (2021-04-05 revision 6847ee089d) [x64-mingw32]

@kenhys
Copy link
Contributor

kenhys commented Sep 30, 2021

If newer msys2 was available, it may be resolved, but not released yet. 🤔

@marciogmorales
Copy link
Author

Hello,
Thanks for the test, but sounds like you built using Windows 10 20H1, right?

Did you try with a server version? I do believe the issue is related to the Server version. I tried both LTSC and 2004.

@kenhys
Copy link
Contributor

kenhys commented Sep 30, 2021

Thanks for the test, but sounds like you built using Windows 10 20H1, right?

Yes, not the server edition.

@marciogmorales
Copy link
Author

marciogmorales commented Oct 7, 2021

Bringing this up again .. Anyone else faced the same issue on a Windows Server version?

@kenhys kenhys added the help wanted Need contributors label Oct 8, 2021
@SumitGITT
Copy link

I am trying the dockerfile provided at the following but the build fails at the copy fluentd.conf step and it says
COPY failed: file not found in build context or excluded by .dockerignore: stat fluent.conf: file does not exist
https://github.com/fluent/fluentd-docker-image/blob/master/v1.14/windows-ltsc2019/Dockerfile

@kanhys, Can you please share the dockerfile if it is working for you already or someone let me know what's happening wrong?

@repeatedly
Copy link
Member

You need to put fluent.conf in building directory.
https://github.com/fluent/fluentd-docker-image/tree/master/v1.14/windows-ltsc2019 includes it.

kenhys added a commit to kenhys/fluentd-docker-image that referenced this issue Feb 4, 2022
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>
kenhys added a commit to kenhys/fluentd-docker-image that referenced this issue Feb 4, 2022
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>
kenhys added a commit that referenced this issue Feb 7, 2022
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Need contributors
Projects
None yet
Development

No branches or pull requests

4 participants