Self-hosted runner: Container has state (exitCode: Some(0), OOMKilled Some(false))

[Raul Laasner]

I'm using the following configuration for my runner which I tried to keep as minimal as possible:

definitions:
  services:
    docker:
      image: ubuntu:20.04
pipelines:
  default:
    - step:
        name: serial release
        runs-on:
          - self.hosted
          - linux
        services:
          - docker
        script:
          - mkdir build && cd build

I keep seeing the following message in Docker output:

Container has state (exitCode: Some(0), OOMKilled Some(false))

The pipeline dashboard doesn't provide anything useful:

+ umask 000

+ GIT_LFS_SKIP_SMUDGE=1 retry 6 git clone --branch="master" --depth 50 https://x-token-auth:$REPOSITORY_OAUTH_ACCESS_TOKEN@bitbucket.org/$BITBUCKET_REPO_FULL_NAME.git $BUILD_DIR

Cloning into '/opt/atlassian/pipelines/agent/build'...

+ git reset --hard 929ea2648e604776bf35ea51ec6c7eb389eb933d

HEAD is now at 929ea26 Update CI

+ git config user.name bitbucket-pipelines

+ git config user.email commits-noreply@bitbucket.org

+ git config push.default current

+ git config http.${BITBUCKET_GIT_HTTP_ORIGIN}.proxy http://localhost:29418/

+ git remote set-url origin http://bitbucket.org/$BITBUCKET_REPO_FULL_NAME

+ git reflog expire --expire=all --all

+ echo ".bitbucket/pipelines/generated" >> .git/info/exclude

+ chmod 777 $BUILD_DIR

Images used:

    build: atlassian/default-image@sha256:3a09dfec7e36fe99e3910714c5646be6302ccbca204d38539a07f0c2cb5902d4

    docker: ubuntu@sha256:3bc6e9f30f51d2bbf9307fc9d0bdfc30caa38cf4e3b05a714230f9a9b3381d84

How would I even begin to debug this? I looked https://community.atlassian.com/t5/Bitbucket-questions/Self-hosted-runner-step-set-up-fails-when-trying-to-use-docker/qaq-p/1764689 but it seems the issue is still up.

[Raul Laasner · Accepted solution]

Never mind, it turns out this is not my real issue. I just need to run some simple tests. Since I'm running docker-public.packages.atlassian.com/sox/atlassian/bitbucket-pipelines-runner:latest which in turns runs my own image I went for the docker-in-docker image solution but apparently that's something else.