Closed lippertmarkus closed 5 months ago
@freddydk any feedback on this?
Sorry, didn't see this before going on vacation - will have a look at this.
@freddydk how is the status on this one?
Until now we had been able to stay on an older the Generic Image version but with the current changes you we are forced to update due to no NextMajor container will start anymore or NextMajor-Pipeline will succeed.
As far as I was able to analyze the issue from @lippertmarkus this happens if you download a zip-file that contains a my folder.
I looks to me like like the condition for the if-block here is not met and the else-block is executed where Move-Item will fail due to the folder c:\run\my already exists.
@freddydk I uploaded a test file for you here: https://glpmtstorage.blob.core.windows.net/cdn/build_main.zip
That one is used in out nextMajor pipelines.
edit: We pull it into the container by adding _-additionalParameters @("--env folders=c:\run=https://glpmtstorage.blob.core.windows.net/cdn/build_main.zip")_ to New-BcContainer.
You can try to add this to your new-bccontainer:
-myscripts @("https://raw.githubusercontent.com/microsoft/nav-docker/master/override/issue512/start.ps1")
I tested it and everything looks good so far. The NextMajor containers start regularly and I did not see any side effect on other containers. Will you create a new generic right away or do you have a release cycle?
new generic images created long ago, assuming it was resolved long ago.
Base Image version v1.0.2.5 works
Build
Run
Base Image version v1.0.2.7 doesn't work
Build
Run
BcContainerHelper version 3.0.10