renovate does not update package-lock.json

[ronaldploeger]

From the FAQ https://docs.renovatebot.com/faq/ I understand that the default behavior is:

Update yarn.lock and/or package-lock.json files if found

and from the configuration docs https://docs.renovatebot.com/configuration-options/#updatelockfiles that the default value for "updateLockFiles" is true.

But for some reason renovate does not update the package-lock.json but only the dependency version in package.json.

This leads to all our build jobs failing as we run "npm ci" which complains:

cipm can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with npm install before continuing.

Are we doing something wrong? Missing a config?

[rarkins]

How you are running Renovate? (self hosted? which image?)

Are you debug logging? What does it say for the branch in question? Note: you must capture the log WHEN the commit is made - running on subsequent runs won't help.

[viceice]

@ronaldploeger How are you running renovate currently? If it's a simple docker container, you can continue this

docker run --rm \
  -v /tmp:/tmp \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -v $PWD/config.js:/src/config.js \
  -w /src \
  -e LOG_LEVEL=debug \
  renovate/renovate:24.49.8-slim

[ronaldploeger]

Hi @rarkins,
this is the full log message:

{"name":"renovate","hostname":"renovate-manual-r85-wgz72","pid":8,"level":20,"logContext":"qlJgPYgvv","repository":"xxx/xxx","branch":"feature-renovate-husky-5.x","err":{"killed":false,"code":1,"signal":null,"cmd":"npm install --package-lock-only --ignore-scripts --no-audit","stdout":"","stderr":"npm ERR! code ENOTSUP\nnpm ERR! notsup Unsupported engine for xxx@0.0.0: wanted: {\"node\":\"12\"} (current: {\"node\":\"14.15.5\",\"npm\":\"6.14.11\"})\nnpm ERR! notsup Not compatible with your version of node/npm: xxx@0.0.0\nnpm ERR! notsup Not compatible with your version of node/npm: xxx@0.0.0\nnpm ERR! notsup Required: {\"node\":\"12\"}\nnpm ERR! notsup Actual: {\"npm\":\"6.14.11\",\"node\":\"14.15.5\"}\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR! /tmp/renovate/cache/others/npm/_logs/2021-02-15T14_35_35_707Z-debug.log\n","message":"Command failed: npm install --package-lock-only --ignore-scripts --no-audit\nnpm ERR! code ENOTSUP\nnpm ERR! notsup Unsupported engine for xxx@0.0.0: wanted: {\"node\":\"12\"} (current: {\"node\":\"14.15.5\",\"npm\":\"6.14.11\"})\nnpm ERR! notsup Not compatible with your version of node/npm: xxx@0.0.0\nnpm ERR! notsup Not compatible with your version of node/npm: xxx@0.0.0\nnpm ERR! notsup Required: {\"node\":\"12\"}\nnpm ERR! notsup Actual: {\"npm\":\"6.14.11\",\"node\":\"14.15.5\"}\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR! /tmp/renovate/cache/others/npm/_logs/2021-02-15T14_35_35_707Z-debug.log\n","stack":"Error: Command failed: npm install --package-lock-only --ignore-scripts --no-audit\nnpm ERR! code ENOTSUP\nnpm ERR! notsup Unsupported engine for xxx@0.0.0: wanted: {\"node\":\"12\"} (current: {\"node\":\"14.15.5\",\"npm\":\"6.14.11\"})\nnpm ERR! notsup Not compatible with your version of node/npm: xxx@0.0.0\nnpm ERR! notsup Not compatible with your version of node/npm: xxx@0.0.0\nnpm ERR! notsup Required: {\"node\":\"12\"}\nnpm ERR! notsup Actual: {\"npm\":\"6.14.11\",\"node\":\"14.15.5\"}\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR! /tmp/renovate/cache/others/npm/_logs/2021-02-15T14_35_35_707Z-debug.log\n\n at ChildProcess.exithandler (child_process.js:308:12)\n at ChildProcess.emit (events.js:315:20)\n at ChildProcess.EventEmitter.emit (domain.js:467:12)\n at maybeClose (internal/child_process.js:1048:16)\n at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)"},"type":"npm","msg":"lock file error","time":"2021-02-15T14:35:35.717Z","v":0}

[ronaldploeger]

@viceice We are running renovate as a k8s CronJob

[viceice]

The logs clearly says: image node version v 14 is not compatible with requested node v12

The best working set i know about renovate and kubernetes is that you need to start a docker dind pod with a shared volume ( /tmp by renovate default) and let renovate slim using that. eg something like:

containers:
  - name: renovate
    image: renovate/renovate:24.11.2-slim
    env:
      - name: DOCKER_HOST
        value: 127.0.0.1
    volumeMounts:
      - name: renovate-tmp-volume
        mountPath: /tmp
  - name: renovate-dind
    image: docker:19.03.14-dind
    env:
    - name: DOCKER_TLS_CERTDIR
      value: ""
    securityContext:
      privileged: true
    volumeMounts:
    - name: renovate-tmp-volume
      mountPath: /tmp
volumes:
  - name: renovate-tmp-volume
    emptyDir: {}

ref #8169

[viceice]

renovatebot/helm-charts#91