figure out what pause image we should use? about sig-windows-dev-tools HOT 9 CLOSED

I dont think the cmd is being processed how we think it is; I see in code where we specify that pod-infra-container but I've checked and on both my linux node and windows node, the infra container is set as "--pod-infra-container-image=k8s.gcr.io/pause:3.4.1" which is the default value for this version of k8s

So, not only does the value we chose not seem to get passed to the kubelet, I'm not sure where the 1.4.0 comes from at all; I just see the 3.4.1 version.

from sig-windows-dev-tools.

Not sure if it is related, but as I was digging around on the windows node, I was trying to find log info and found the IIS logs:

2021-08-02T13:16:15.1042915-07:00 stdout F 
2021-08-02T13:16:15.1209022-07:00 stdout F Success Restart Needed Exit Code      Feature Result                           
2021-08-02T13:16:15.1229949-07:00 stdout F ------- -------------- ---------      --------------                           
2021-08-02T13:16:15.1270207-07:00 stdout F True    No             Success        {Common HTTP Features, Default Documen...
2021-08-02T13:16:27.5225856-07:00 stderr F Invoke-WebRequest : The remote name could not be resolved: 
2021-08-02T13:16:27.5225856-07:00 stderr F 'dotnetbinaries.blob.core.windows.net'
2021-08-02T13:16:27.5225856-07:00 stderr F At line:1 char:32
2021-08-02T13:16:27.5225856-07:00 stderr F + ... Web-Server; Invoke-WebRequest -UseBasicParsing -Uri 'https://dotnetbi ...
2021-08-02T13:16:27.5235999-07:00 stderr F +                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2021-08-02T13:16:27.5237153-07:00 stderr F     + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:Htt 
2021-08-02T13:16:27.5237153-07:00 stderr F    pWebRequest) [Invoke-WebRequest], WebException
2021-08-02T13:16:27.5237153-07:00 stderr F     + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShe 
2021-08-02T13:16:27.5237153-07:00 stderr F    ll.Commands.InvokeWebRequestCommand
2021-08-02T13:16:27.5237153-07:00 stderr F  
2021-08-02T13:16:27.5597505-07:00 stderr F C:\ServiceMonitor.exe : The term 'C:\ServiceMonitor.exe' is not recognized as 
2021-08-02T13:16:27.5597505-07:00 stderr F the name of a cmdlet, function, script file, or operable program. Check the 
2021-08-02T13:16:27.5597505-07:00 stderr F spelling of the name, or if a path was included, verify that the path is 
2021-08-02T13:16:27.5597505-07:00 stderr F correct and try again.
2021-08-02T13:16:27.5597505-07:00 stderr F At line:1 char:311
2021-08-02T13:16:27.5597505-07:00 stderr F + ... ml>' > C:\inetpub\wwwroot\default.html; C:\ServiceMonitor.exe 'w3svc' ...
2021-08-02T13:16:27.5597505-07:00 stderr F +                                             ~~~~~~~~~~~~~~~~~~~~~
2021-08-02T13:16:27.5597505-07:00 stderr F     + CategoryInfo          : ObjectNotFound: (C:\ServiceMonitor.exe:String) [ 
2021-08-02T13:16:27.5597505-07:00 stderr F    ], CommandNotFoundException
2021-08-02T13:16:27.5597505-07:00 stderr F     + FullyQualifiedErrorId : CommandNotFoundException
2021-08-02T13:16:27.5597505-07:00 stderr F  
2021-08-02T13:16:27.5607791-07:00 stdout F 
2021-08-02T13:16:27.5607791-07:00 stdout F 

In addition, I'm not certain about the networking/sockets on windows. I tried something simple like ctr containers list and it complains about permission denied to the socket address.

from sig-windows-dev-tools.

For that first issue; it seems we download that binary and try to invoke it. I hate powershell for making things like that hard but I'm experimenting with just running it via Start-Process ... -ArgumentList and seeing if that helps IIS and cluster health in general.

from sig-windows-dev-tools.

I found the kubeadm-flags.env file and shows 3.4.1 version:

KUBELET_KUBEADM_ARGS="--container-runtime=remote --container-runtime-endpoint=npipe:////./pipe/containerd-containerd --pod-infra-container-image=k8s.gcr.io/pause:3.4.1"

from sig-windows-dev-tools.

Ahh thanks
Make sure to rebase on master I just fixed some issues w calico.

from sig-windows-dev-tools.

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

from sig-windows-dev-tools.

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

from sig-windows-dev-tools.

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

from sig-windows-dev-tools.

@k8s-triage-robot: Closing this issue.

from sig-windows-dev-tools.