Open davidaparicioalvarez opened 7 months ago
freddydk
commented
7 months ago Please provide as much information as possible in order for us to help you.
It looks like you are using a self-hosted runner, is that true? How did you create that? What did you install on that? Did you try with standard GitHub hosted Windows runners? Does that work?
samlehm
commented
7 months ago Have the same problem since yesterday.
All Docker Server (3), running since 2 month without problems have now the same issue. No OS CU update or other works on this servers the last days/weeks.
Last 10h we tried this: Installed latest OS CU update Checked disk space Restarted server docker system prune docker system prune -a Docker Update - Docker Engine v25.0.3 add this parameters { "experimental": false, "storage-opts" ["size=20GB"] } ReRun in DevOps old pipelines - now the have the same issue:
Stopping Business Central Service Tier Installation took 221 seconds Installation complete New-Bcimage Telemetry Correlation Id: 0b5e57d1-a660-45da-8afa-951067727c27 New-BcContainer Telemetry Correlation Id: 93c58d92-b006-498a-a981-1734a7fc582f Removing Desktop shortcuts Run-AlPipeline Telemetry Correlation Id: 5b43bb3e-be2c-46d6-9751-19af4f43a549
specified. (0x3) ExitCode: 1 Commandline: docker build --isolation=process --memory 64G --no-cache --tag bcimage:sandbox-23.4.15643.16247-ch-mt c:\bcartifacts.cache\auqb2lq4.b31 At C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\6.0.5\ContainerHandling\New-NavImage.ps1:700 char:27
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,DockerDo
##[error]PowerShell exited with code '1'.
Finishing: Run Pipeline
davidaparicioalvarez
commented
7 months ago Hi, I remove and reinstall all software, but same error
It looks like you are using a self-hosted runner, is that true? Yes, it is a local runner windows server 2022
How did you create that? Using instructions at https://github.com/APAWARE/SPANISHKITS/settings/actions/runners
What did you install on that? Windows, Docker, Bc-Containerhelper, Git, GitHUb CLI Docker versión Client: Version: 25.0.3 API version: 1.42 (downgraded from 1.44) Go version: go1.21.6 Git commit: 4debf41 Built: Tue Feb 6 21:13:02 2024 OS/Arch: windows/amd64 Context: default
Server: Mirantis Container Runtime Engine: Version: 23.0.9 API version: 1.42 (minimum version 1.24) Go version: go1.20.12m1 X:boringcrypto Git commit: a9047f2f86 Built: OS/Arch: windows/amd64 Experimental: false
Bc-ContainerHelper 6.0.5 Git git version 2.43.0.windows.1 GitHub Cli https://github.com/cli/cli/releases/tag/v2.43.1
Did you try with standard GitHub hosted Windows runners? No, I cannot use GitHub hosted, No runnner get the job.
Does that work? I don't know
davidaparicioalvarez
commented
7 months ago logs_181.zip Installed all from scratch, Windows also. Same error.
davidaparicioalvarez
commented
7 months ago I think, it is a self-hosted software error...... it is running in a GitHub hosted Windows runner and no errors.
davidaparicioalvarez
commented
7 months ago Solved, new installation from scratch, with Docket and GirHub in Windows Server core 2022, now working
freddydk
commented
7 months ago You can also use https://aka.ms/getbuildagent to create and register a build agent on Azure - that should have all pre-requisites.
AskeHolst
commented
7 months ago I see the same issue on one of our self-hosted runners, all were created with https://aka.ms/getbuildagent so there should not be any difference, but I guess there is. Strangely it only failed for countries where a newer artifact was used, when it reused an older it kept working. So we had a day of ES builds failing, but GB builds working as an example. I might just try to spin up a new runner over the weekend.
samlehm
commented
7 months ago Maybe MS solved the problem or the removing of the two parameters "cacheImage", "CreateRuntimePackages" in settings.json helped.
settings.json { "version": "current", "artifact": "///ch/Current", "cacheImage": true, "CreateRuntimePackages": true },
freddydk
commented
7 months ago I think you guys are seeing different problems giving the same error. The ImportLayer error @davidaparicioalvarez is talking about was fixed by a reinstall (so he says) @samlehm - you reported an error with a specific version of BC when using cacheImage (i.e. building an image just-in-time) - that is probably a bug - if you can provide the script used to provoke this? - please create a new issue? @AskeHolst - what artifacts are you using? is this nextmajor?
Hi,
I run a CI/CD action and raise an error during Creating container: