Closed J-KVS closed 3 years ago
I think this is because of Hyperv isolation - try to remove that
Thank you for the rapid response. Yes, with process isolation I don't have this error. But I get other problems when I choose process isolation. Would it be possible to fix my initial problem with a hyper v isolation?
It is a docker/Windows version issue, not something I can do anything about, sorry.
Ok, in this case we can close this issue and I'll have to open another issue for my problems with process isolation.
Hi @J-KVS , Were you able to solve the problem with the isolation process ? Thanks
Hi @IvanArsov,
I switched from working on my local Windows Version to a Windows Server in Azure and had since no problems.
Just change the timezone in the container like
$containerName = 'myContainer'
$scriptBlock = {
Set-TimeZone -Id "Central European Standard Time"
}
Invoke-ScriptInBCContainer -containerName $containerName -scriptblock $scriptBlock
Describe the issue If I try to execute a codunit inside the container the following error occures:
The time zone with ID 'Mitteleuropäische Zeit' was not recognized on the server. Update your computer's time zone definitions.
OS: Microsoft Windows 10 Enterprise Version: 10.0.18363 Build 18363 Localization: Germany
Please let me know if you need additional information.
Scripts used to create container and cause the issue
Full output of scripts
Screenshots
Additional context