Open horstoeko opened 7 months ago
This command tries to use a pre-build image to create the container. If you specify -imageName "" - then you should avoid this step and you can see whether that makes a difference
Hi @freddydk,
Thanks for the tip. We have temporarily adjusted our build infrastructure and added the -imageName ""
parameter (as you mentioned). Now a container is created. However, the runtime is of course much longer. From our point of view, this can of course only be a temporary solution. ;-)
Try to recreate the image, maybe docker was updated and the image is no longer valid.
Hi!
Deleting all images seems to have solved the problem. We will continue to monitor this.
Hi!
A small update: After deleting the my
-images yesterday and setting up a new one, everything worked to our satisfaction. This morning the same problem occurred again (after our infrastructure was restarted). Apart from a reboot, nothing was changed in the infrastructure - nor was Docker updated in any way.
You could try to run the cleanup tool from this old blog post: https://freddysblog.com/2018/12/11/clean-up-after-yourself-docker-your-mom-isnt-here/ - the docker file system contains a lot of symbolic links and if any of this goes bad - then you might have stuff in there, which fails everytime somebody touches it.
Hi
Since a few days it is no longer possible to get Run-ALPipeline to build a container. The process aborts with the following error:
Full output of scripts
We have tried various things, but unfortunately without success. However, the containers can be created manually via Powershell. So (in our opinion) this does not seem to be a direct problem with Docker.
Many thanks in advance for your support and a possible solution to the problem.