You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I realised today I cannot recreate local dev containers anymore.
It might be an issue with docker desktop v4.27.2
Error: No such object: failed to get console mode for stdout: The handle is invalid.
Run-AlPipeline Telemetry Correlation Id: 7881398b-4d32-4f8d-98ad-3676778da0d2
Error: Invalid JSON primitive: failed.
Stacktrace: at Test-BcContainer, C:\ProgramData\BcContainerHelper\6.0.6-preview1131\BcContainerHelper\ContainerInfo\Test-NavContainer.ps1: line 34
at <ScriptBlock>, C:\ProgramData\BcContainerHelper\6.0.6-preview1131\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 989
at <ScriptBlock>, C:\ProgramData\BcContainerHelper\6.0.6-preview1131\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 966
at <ScriptBlock>, C:\ProgramData\BcContainerHelper\6.0.6-preview1131\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 948
at Run-AlPipeline, C:\ProgramData\BcContainerHelper\6.0.6-preview1131\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 910
at CreateDevEnv, C:\Users\JonasWrede\AppData\Local\Temp\tmp785E.tmp.ps1: line 1894
at <ScriptBlock>, C:\Users\JonasWrede\Projects\byndit\App\.AL-Go\localDevEnv.ps1: line 128
at <ScriptBlock>, <No file>: line 1
I think the issue is that docker inspect can't find a container
$inspect = docker inspect $id | ConvertFrom-Json
Has anybody encountered it?
The text was updated successfully, but these errors were encountered:
Yeah, this was reported here microsoft/navcontainerhelper#3326 as well.
Nothing really we can do about that until docker releases 4.28.0
Personally, I use docker engine only, which doesn't have this problem.
Hi, I realised today I cannot recreate local dev containers anymore.
It might be an issue with docker desktop v4.27.2
I think the issue is that docker inspect can't find a container
Has anybody encountered it?
The text was updated successfully, but these errors were encountered: