microsoftgraph / microsoftgraph/msgraph-sdk-powershell

Memory issue when running in Docker Desktop

Open
#2,246 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type:bug
Dominant language
C#
Stars
898
Forks
230
Avg merge
2d 5h
Merged PRs (30d)
31

Description

Describe the bug

I try to run the latest image on mac os and after the container started and send the Connect-Graph command the console write this error: "Fatal error. System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

To Reproduce
Steps to reproduce the behavior:

  1. Run with interactive: docker run -it mcr.microsoft.com/microsoftgraph/powershell
  2. And send the following command: Connect-Graph

Expected behavior

I can login to Microsoft Grap.

Debug Output

PS /> Connect-Graph -Debug
Fatal error. System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other > memory is corrupt.
at System.String.IsNullOrEmpty(System.String)
at System.Management.Automation.ParameterAttribute.set_ParameterSetName(System.String)
at DynamicClass.CallSite.Target(System.Runtime.CompilerServices.Closure, System.Runtime.CompilerServices.CallSite, > > System.String, System.Management.Automation.ExecutionContext)
qemu: uncaught target signal 6 (Aborted) - core dumped

Module Version

PS /> Get-Module Microsoft.Graph
PS /> Get-Module

ModuleType Version PreRelease Name ExportedCommands


Script 2.2.6 PSReadLine {Get-PSReadLineKeyHandler, Get-PSReadLineOption, Remove-> PSReadLineKeyHandler, Set-PSReadLineKeyHandler…}

The Get-Module Microsoft.Graph* or Get-Module Microsoft.Graph command has no output at all.

Environment Data

PS /> $PSVersionTable

Name Value


PSVersion 7.3.4
PSEdition Core
GitCommitId 7.3.4
OS Linux 5.15.49-linuxkit-pr #1 SMP PREEMPT Thu May 25 07:27:39 UTC 2023
Platform Unix
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0

Additional context

My Environment:
Macbook Pro M1 (Apple Silicon)
Mac OS 13.4.1 (c)
Docker Desktop 4.21.1 (114176)

In the Docker Desktop has 4CPU, 4GB RAM, 20 GB Storage. After the container started, the allocated memory is 1.8GB.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with docker run -it mcr.microsoft.com/microsoftgraph/powershell on an Apple Silicon Mac, then run Connect-Graph and compare the reported PowerShell and Docker environment details. Done means the container can execute Connect-Graph and reach the Microsoft Graph login without an AccessViolationException.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, macos, powershell
Domain
cli, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.