Skip to content

Conversation

@paulgmiller
Copy link
Member

@paulgmiller paulgmiller commented Aug 22, 2024

Shellig out to powershell while sometimes convenient has a couple of issues

  1. large bump of memory inside your contaienr as the whole dotnetframework comes to ife
  2. dependency on customer not muckign with host powrshell since we run in host namespace? (could use powershell core in our contaienr?)
  3. parsing std out isnt always the best.

Reason for Change:

Custoemr reporting ooms on azure-windows-cns.

Issue Fixed:

Requirements:

Notes:

…s a gob of memory, 2) its a large dependency that can be corrupted in hos process maybe
@paulgmiller paulgmiller requested a review from a team as a code owner August 22, 2024 18:30
@paulgmiller paulgmiller requested a review from pjohnst5 August 22, 2024 18:30
@rbtr
Copy link
Collaborator

rbtr commented Aug 23, 2024

/azp run Azure Container Networking PR

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@rbtr
Copy link
Collaborator

rbtr commented Aug 23, 2024

cc @QxBytes

@rbtr rbtr self-assigned this Aug 23, 2024
@rbtr rbtr requested review from behzad-mir, rbtr and tamilmani1989 and removed request for pjohnst5 August 23, 2024 15:23
@rbtr rbtr added cns Related to CNS. windows labels Aug 23, 2024
@rbtr
Copy link
Collaborator

rbtr commented Aug 28, 2024

we're gonna do it, but closing this one in favor of #2961

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

Labels

cns Related to CNS. windows

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants