This happens using a self-hosted runner. Everything was working until recently.
See below the runner logs:
[2022-03-22 10:46:04,174] Starting container.
[2022-03-22 10:46:04,364] Adding container log: /var/lib/docker/containers/4601662430cff842653feeb26e5dac62121f6f0cbd7f6d26754e8e33a99917a5/4601662430cff842653feeb26e5dac62121f6f0cbd7f6d26754e8e33a99917a5-json.log
[2022-03-22 10:46:04,365] Waiting on container to exit.
[2022-03-22 10:46:04,590] Adding container log: /var/lib/docker/containers/79e4dc280afe792d5f502db987cfdf2be3a99d08feea48261063c645b291e210/79e4dc280afe792d5f502db987cfdf2be3a99d08feea48261063c645b291e210-json.log
[2022-03-22 10:46:04,590] Waiting on container to exit.
[2022-03-22 10:46:04,593] Creating exec into container.
[2022-03-22 10:46:04,597] Starting exec into container and waiting for exec to exit.
[2022-03-22 10:46:04,902] Container has state (exitCode: Some(1), OOMKilled Some(false))
[2022-03-22 10:46:04,907] Removing container fb23e655-e801-5080-85d3-0ceba516a714_ac54a500-c8ce-467e-a0d7-2c45cdf5fe93_build
[2022-03-22 10:46:04,913] Not uploading caches. (numberOfCaches: 0, resultOrError: ERROR)
[2022-03-22 10:46:04,915] Not uploading artifacts. (numberOfArtifacts: 0, resultOrError: ERROR)
[2022-03-22 10:46:04,915] Updating step progress to PARSING_TEST_RESULTS.
[2022-03-22 10:46:05,339] Appending log line to main log.
[2022-03-22 10:46:05,342] Appending log line to log: {1df70d82-c8e6-49a5-b641-2d512016bfd6}.
[2022-03-22 10:46:05,384] Test report processing complete.
[2022-03-22 10:46:05,384] Removing container fb23e655-e801-5080-85d3-0ceba516a714_ac54a500-c8ce-467e-a0d7-2c45cdf5fe93_clone
[2022-03-22 10:46:05,399] Removing container fb23e655-e801-5080-85d3-0ceba516a714_ac54a500-c8ce-467e-a0d7-2c45cdf5fe93_clone
[2022-03-22 10:46:05,404] Removing container fb23e655-e801-5080-85d3-0ceba516a714_ac54a500-c8ce-467e-a0d7-2c45cdf5fe93_build
[2022-03-22 10:46:05,408] Removing container fb23e655-e801-5080-85d3-0ceba516a714_ac54a500-c8ce-467e-a0d7-2c45cdf5fe93_system_auth-proxy
[2022-03-22 10:46:05,563] Removing container fb23e655-e801-5080-85d3-0ceba516a714_ac54a500-c8ce-467e-a0d7-2c45cdf5fe93_pause
[2022-03-22 10:46:05,878] Updating step progress to COMPLETING_LOGS.
[2022-03-22 10:46:06,341] Appending log line to main log.
[2022-03-22 10:46:06,395] Shutting down log uploader.
[2022-03-22 10:46:07,391] Tearing down directories.
[2022-03-22 10:46:07,394] Cancelling timeout
[2022-03-22 10:46:07,396] Completing step with result Result{status=ERROR, error=Some(Error{key='runner.bitbucket-pipelines.clone-container-failure', message='/tmp/fb23e655-e801-5080-85d3-0ceba516a714/tmp/clone_result', arguments={}})}.
[2022-03-22 10:46:07,862] Setting runner state to not executing step.
[2022-03-22 10:46:07,863] Waiting for next step.
[2022-03-22 10:46:22,650] Updating runner state to "ONLINE".
I had my working set to '/tmp'
Also a volume 'tmp/bitbucket' pointing to '/tmp'
somehow that configuration creates '/tmp/hash/tmp/clone_result' instead of '/tmp/bitbucket/hash/tmp/clone_result'
I changed my volume back to '/tmp' and it worked again.
I cant remember how or why I changed it to be '/tmp/bitbucket' though.
Thank you Pravin and Norbert from bitbucket support for your help
Hello.. I'm facing the same issue, when starting container on RHEL machine, it get stuck in cloning step and logs aren't showing much details.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.