In case of self-hosted runners as Linux Docker, and I'm using pipe s3 deploy,
Where does the pipe run ? Does it run and create docker images on the host machine or in bitbucket infrastructure agent?
Thank you Syahrul,
Got it. but can you tell me in case of self-hosted runners as Linux Docker,
I see that each step an image is pulled and a container is run but I can't see those containers on the host except the one of the runner it self. So, where are these containers run?
Hey @Moamen Yousef
This is expected since the runner log only shows runner information, and the pipe runs on a docker container. If you wish to see the log, you can run the following commands on your host:
docker logs --details --follow <containerUUID>
When the build is triggered, you can get the container UUID in the runner log. Locate the container UUID that has _build at the end. This should show the whole build logs, which include the pipe.
Also, the container is removed when the build is complete; hence you can't locate it in your host. This can be seen in your runner log, it should mention something similar as this:
[2022-08-16 04:01:56,933] Removing container 44563242-9239-5082-8659-b3fce1d8bb67_cd1e32cb-1dc3-40f1-9ca6-f2d3d5e522f5_clone
[2022-08-16 04:01:56,964] Removing container 44563242-9239-5082-8659-b3fce1d8bb67_cd1e32cb-1dc3-40f1-9ca6-f2d3d5e522f5_clone
[2022-08-16 04:01:56,969] Removing container 44563242-9239-5082-8659-b3fce1d8bb67_cd1e32cb-1dc3-40f1-9ca6-f2d3d5e522f5_build
I hope this helps.
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...