When running CI for techdocs, the image is being built twice I think.
Once for make VERBOSE=all validate-static build-images and once for make VERBOSE=all -j4 test.
For example, see https://github.com/coopnorge/engineering-docker-images/actions/runs/3497854509/jobs/5857473124#step:14:44
It is not shown explicitly, but the time being spent here:
2022-11-18T14:54:10 7095 140263151953728 010:DEBUG urllib3.connectionpool connectionpool:456:_make_request http://localhost:None "POST /v1.41/build?q=False&nocache=False&rm=False&forcerm=False&pull=False HTTP/1.1" 200 None
2022-11-18T14:57:33 7095 140263151953728 010:DEBUG urllib3.connectionpool connectionpool:456:_make_request http://localhost:None "GET /v1.41/images/db7984182366/json HTTP/1.1" 200 None
Is inside the build_image function.
I have noticed the same thing on my computer. I'm unsure of why it is happening, but it is. I think it may be because of the way the tests are written and how it interacts with docker daemon.
When running CI for techdocs, the image is being built twice I think.
Once for
make VERBOSE=all validate-static build-imagesand once formake VERBOSE=all -j4 test.For example, see https://github.com/coopnorge/engineering-docker-images/actions/runs/3497854509/jobs/5857473124#step:14:44
It is not shown explicitly, but the time being spent here:
Is inside the
build_imagefunction.I have noticed the same thing on my computer. I'm unsure of why it is happening, but it is. I think it may be because of the way the tests are written and how it interacts with docker daemon.