Closed dominicstarkl closed 4 years ago
The build servers did suffer from some February update problems and some images might have been wrongly build. These should have been updated - if you can assure me, that you used -alwaysPull (cannot see the value of the variable above) then I will have a look and rebuild the image.
Hy Freddy
Many thanks for your quick response.
We never use -alwaysPull because of performance issues. But I can assure you that I pulled the above mentioned Docker image at the same time I tried to create the Docker container from it. This is also written in the Event Protocol:
[...]
Status: Downloaded newer image for mcr.microsoft.com/businesscentral/onprem:14.10.40471.0-ch-ltsc2019
[...]
In the meantime, I created my desired Docker container using the DVD Path with -dvdPath, and this worked without any issues.
Nevertheless, I think it could be worthful, if you rebuild the wrongly built Docker images to avoid that other users run into the same issues a I did.
Thanks again for your help!
Regards Dominic
Will check that image when I get back from vacation. Issue is, that I don't know which images were wrongly build - I thought I rebuild all. Thanks for all the info.
Hi Freddy Thanks for your information. I whish you a pleasant vaccation! Regards Dominic
Hi, I'm quite newbie with these, but I probably found same error with following concept:
-accept_eula
-imageName $imagename -auth $auth
-licenseFile $license `
-useTraefik @beemubotokka - that looks like a totally different issue. Please create a new issue and include the full output from the command, thanks
We have an issue in creating a Docker container from a specific Business Central OnPrem image. The creation of the container exists with an error and the container is unhealthy.
Related image mcr.microsoft.com/businesscentral/onprem:14.10.40471.0-ch-ltsc2019
Docker info
The container is created using NavContainerHelper, version 0.6.5.0
Container tries to be created with following command:
We can create containers from other BC OnPrem images in the same way as described above without any issues.
Full event protocol until the error occurs:
The EventLog of the so created unhealthy Docker container writes following entries for example:
It seems as if no connection can be made with the internal SQL database.
Thank you for verifying and reporting back this issue.
Regards