Skip to content

Conversation

olljanat
Copy link

Continuation for #872 to also provide container images for Windows Server 2025

@olljanat olljanat requested a review from a team as a code owner August 22, 2025 12:32
@olljanat olljanat requested a review from dehaansa August 22, 2025 12:32
@mowies mowies changed the title packaging: Start producing container images for Windows 2025 (#339) packaging: Start producing container images for Windows 2025 Aug 25, 2025
Copy link
Member

@mowies mowies left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please add a changelog entry by copying the .chloggen/TEMPLATE.yaml file and filling it out

@olljanat olljanat marked this pull request as draft August 27, 2025 06:11
@olljanat
Copy link
Author

olljanat commented Aug 27, 2025

please add a changelog entry by copying the .chloggen/TEMPLATE.yaml file and filling it out

Ah, it needs to be copied. Was just confused as there it no any other files on that folder but I see now that release process removes those.

Anyway, I see at least contrib collector crashing in start when build for Win 2025 because it depends on some DLLs which does not exists in that version of nanoserver image anymore so converted to draft for now.

@douglascamata
Copy link
Member

Anyway, I see at least contrib collector crashing in start when build for Win 2025 because it depends on some DLLs which does not exists in that version of nanoserver image anymore so converted to draft for now.

@olljanat do you happen to know if such DLL will ever be included in the win 2025 nanoserver image? Asking because if it won't, I think it's fine for us to use a "bigger" base image for win 2025 so that we can support this version of Windows.

@olljanat
Copy link
Author

olljanat commented Sep 5, 2025

I would guess that no. Normally Microsoft just remove components from nanoserver but let’s wait that open-telemetry/opentelemetry-collector-contrib#42297 is merged before evaluation of “bigger” image.

@pjanotti
Copy link
Contributor

pjanotti commented Sep 5, 2025

Anyway, I see at least contrib collector crashing in start when build for Win 2025 because it depends on some DLLs which does not exists in that version of nanoserver image anymore so converted to draft for now.

@olljanat can you share the exact error message that you are getting?

Copy link
Contributor

@pjanotti pjanotti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change itself LGTM - I'm just want to understand the error mentioned about a missing DLL.

Copy link
Contributor

This PR was marked stale due to lack of activity. It will be closed in 14 days.

@github-actions github-actions bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Sep 20, 2025
@mowies mowies removed the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Sep 22, 2025
@pjanotti
Copy link
Contributor

Ping @olljanat - do you plan to get back to this one?

@olljanat
Copy link
Author

I'm just want to understand the error mentioned about a missing DLL.

Sorry about delay. Error is:

panic: Failed to find PdhOpenQuery procedure in pdh.dll: The specified procedure could not be found.

goroutine 1 [running]:
syscall.(*DLL).MustFindProc(...)
        syscall/dll_windows.go:127
github.com/open-telemetry/opentelemetry-collector-contrib/pkg/winperfcounters/internal/third_party/telegraf/win_perf_counters.init.1()
        github.com/open-telemetry/opentelemetry-collector-contrib/pkg/winperfcounters@v0.136.0/internal/third_party/telegraf/win_perf_counters/pdh.go:199 +0x411

do you happen to know if such DLL will ever be included in the win 2025 nanoserver image? Asking because if it won't, I think it's fine for us to use a "bigger" base image for win 2025 so that we can support this version of Windows.

Yes using mcr.microsoft.com/windows/servercore:ltsc2025-amd64 as base image fixes that DLL error so I think that it is needed.

do you plan to get back to this one?

Not sure what it right place handle that exception?

@olljanat olljanat closed this Sep 29, 2025
@olljanat olljanat reopened this Sep 29, 2025
@pjanotti
Copy link
Contributor

Thanks for the details @olljanat - at first PdhOpenQuery is in the list of supported APIs per this doc. 🤔 I'm going to look into this ...

@pjanotti
Copy link
Contributor

The attempt to find the proc PdhOpenQuery comes from pkg/winperfcounters/internal/third_party/telegraf/win_perf_counters/pdh.go since various other succeeded before this one failing I think we should attempt to fix this by fixing the package code.

@pjanotti
Copy link
Contributor

pjanotti commented Sep 30, 2025

Just confirmed from the 2025 nano image:

          1    0 00001B60 PdhAddCounterW
          2    1 00001C70 PdhAddEnglishCounterW
          3    2 00001D80 PdhCalculateCounterFromRawValue
          4    3 00001EA0 PdhCloseLog
          5    4 00001FA0 PdhCloseQuery
          6    5 00002190 PdhCollectQueryData
          7    6 00002090 PdhCollectQueryDataEx
          8    7 00002280 PdhEnumObjectItemsW
          9    8 000023F0 PdhEnumObjectsW
         10    9 00002510 PdhExpandCounterPathW
         11    A 00002610 PdhExpandWildCardPathW
         12    B 00002730 PdhGetCounterInfoW
         13    C 00002840 PdhGetFormattedCounterArrayW
         14    D 00002960 PdhGetFormattedCounterValue
         15    E 00002A70 PdhGetRawCounterValue
         16    F 00002B70 PdhOpenLogW
         17   10 000031F0 PdhOpenQueryH
         18   11 00002CB0 PdhOpenQueryW
         19   12 00002DB0 PdhRemoveCounter
         20   13 00002EA0 PdhUpdateLogW
         21   14 00002FB0 PdhValidatePathW

so there is no PdhOpenQuery we have to use PdhOpenQueryW directly instead of relying on the extra symbol available on the pdh.dll shipped on the other Windows images.

Copy link
Contributor

This PR was marked stale due to lack of activity. It will be closed in 14 days.

@github-actions github-actions bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Oct 15, 2025
@douglascamata
Copy link
Member

Hey @olljanat, let us know if you still plan to work on this so that we remove the stale label in this case. Thank you!

@olljanat olljanat closed this Oct 15, 2025
@olljanat
Copy link
Author

Closed for now as migration to PdhOpenQueryW mentioned above needs to be done first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

os:windows stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants