I have a CI/CD job that is supposed to build me a DB2 image from a local harbor directory using kaniko.

Once build this image is published on this harbor directory.

Here's my DB2 container build job:

db2-build:
  extends: .kaniko_job
  tags:
    - kubernetes
  stage: container-build
  image:
    name: gcr.io/kaniko-project/executor:debug
    entrypoint: [""]
  variables:
    CONTEXT_DIR: "container/db2"
    CONTAINERFILE_PATH: "container/db2/Containerfile"
    IMAGE_PATH: "${CI_PROJECT_PATH}/db2"
    KANIKO_ARGS: "--verbosity=debug --build-arg PJ_USER_USERNAME=${PJ_USER_USERNAME} --build-arg PJ_USER_PASSWORD=${PJ_USER_PASSWORD} --build-arg WAS_VERSION=${WAS_VERSION} --build-arg FRAMEWORK_VERSION=${FRAMEWORK_VERSION} --build-arg CIOBS_VERSION=${CIOBS_VERSION} --build-arg RNRPP_HOSTNAME=${RNRPP_HOSTNAME} --build-arg CACLR_HOSTNAME=${CACLR_HOSTNAME}"
  needs: ["maven-build-test"]
  rules:
    - if: $task == "container-build"
    - if: $task == null && $MANUAL_CONTAINER_BUILD == "false" && $CI_COMMIT_BRANCH == "main"

And here's my kaniko job from which the DB2 job inherits:

   .kaniko_job:
      stage: container-build
      tags:
        - kubernetes
      image:
        name: arhs-harbor.arhs-developments.com/library/kaniko:1.9.1
        entrypoint: [""]
      timeout: 1h
      variables:
        IMAGE_PATH: ""
        CONTEXT_DIR: "${CI_PROJECT_DIR}"
        KANIKO_ARGS: ""
        CONTAINERFILE_PATH: "$CONTEXT_DIR/Containerfile"
      script:
        - mkdir -p /kaniko/.docker
        - /kaniko/executor version
        - echo "{\"auths\":{\"$CI_REGISTRY\":{\"username\":\"$CI_REGISTRY_USER\",\"password\":\"$CI_REGISTRY_PASSWORD\"}}}" > /kaniko/.docker/config.json
        - echo "${KANIKO_ARGS}"
        - |
          /kaniko/executor $KANIKO_ARGS \
            --ignore-path=/usr/bin/ping \
            --ignore-path=/usr/bin/newgidmap \
            --ignore-path=/usr/bin/newuidmap \
            --ignore-path=/usr/sbin/arping \
            --ignore-path=/usr/sbin/clockdiff \
            --cache-copy-layers \
            --cache \
            --cache-ttl 24h \
            --context $CONTEXT_DIR \
            --dockerfile $CONTAINERFILE_PATH \
            --destination $CI_REGISTRY/$IMAGE_PATH:$CI_COMMIT_SHA \
            --destination $CI_REGISTRY/$IMAGE_PATH:$CI_COMMIT_REF_SLUG

This job used to work perfectly, but for the past 3 weeks I've been getting this error:

+ db2stop force SQL6037N START or STOP DATABASE MANAGER timeout value was reached. error building image: error building stage: failed to execute command: waiting for process to exit: exit status 10 Cleaning up project directory and file based variables 00:01 ERROR: Job failed: command terminated with exit code 10

This error only occurs on the Gitlab runner. FYI, I use the kubernetes executor and my runner runs via a pod

I'm trying to debug by trying to retrieve the logs, but I can't find any information or apparent error to tell me more about this pipeline failure.

However, locally, the container is building, so there's no problem. I even tried to empty the DB2 caches generated, but no way.

I also tried the debug version (as used above), I tried to downgrade and upgrade the kaniko version but no way.

If anyone can help me understand this error or get more information, I'd love to hear from you.

UPDATE link to my log files :

0

There are 0 answers