mise: Add mise to the renovate docker image

[aidanleuck]

How are you running Renovate?

Self-hosted Renovate CLI

Which platform you running Renovate on?

GitHub.com

Which version of Renovate are you using?

43.216.0

Please tell us more about your question or problem

Summary

Renovate has supported mise lockfile maintenance
since that feature landed in the manager. However, the Renovate base Docker image does not currently
have mise installed, which means lockfile maintenance cannot actually execute mise install inside
the container.

Problem

When lockfileMaintenance is enabled for a repository that uses a mise.lock file, Renovate needs to
run mise install inside the container to regenerate the lockfile. Without mise present in the image,
this step will fail.

Logs (if relevant)

INFO: Renovate is exiting with a non-zero code due to the following logged errors
10:46:19         "loggerErrors": [
10:46:19           {
10:46:19             "name": "renovate",
10:46:19             "level": 50,
10:46:19             "logContext": "13ebbf16-a8a1-4e2b-ad64-0e55f6b1a1ca",
10:46:19             "repository": "SEL-Information-Services/ffdo-container-distribution-ffdo-base",
10:46:19             "branch": "renovate/node-24.x-lockfile",
10:46:19             "err": {
10:46:19               "errno": -2,
10:46:19               "code": "ENOENT",
10:46:19               "syscall": "spawn mise",
10:46:19               "path": "mise",
10:46:19               "spawnargs": ["trust", "config.toml"],
10:46:19               "message": "spawn mise ENOENT",
10:46:19               "stack": "Error: spawn mise ENOENT\n    at Process.ChildProcess._handle.onexit (node:internal/child_process:287:19)\n    at onErrorNT (node:internal/child_process:508:16)\n    at processTicksAndRejections (node:internal/process/task_queues:90:21)"
10:46:19             },
10:46:19             "msg": "unhandledRejection"
10:46:19           }
10:46:19         ]

[jamietanna]

Mind sharing more logs? That seems interesting and like perhaps we're not making sure we're noting that the tool needs to be installed dynamically (via install-tool)

[aidanleuck]

The important log line that I found was this one

DEBUG: Ignoring tool contraints because of `binarySource=global` (repository=SEL-Information-Services/ffdo-container-distribution-ffdo-base, branch=renovate/node-24.x-lockfile)

It appears that the env for the renovate-full docker image expects all tools to be available and none to be fetched at runtime. See

renovate/tools/docker/Dockerfile

Line 15 in 3f697a4

ENV RENOVATE_BINARY_SOURCE=global

I was able to get around the issue by overriding the binarySource to install, however it seems like the full image kind of expects that all tools are present? Maybe just need a doc update that if you are using the full image you should set binarySource to install instead?

[jamietanna]

Aha! I didn't realise we didn't have it in https://github.com/renovatebot/base-image/blob/main/Dockerfile - fancy raising a PR? If not, I can do :)

[jamietanna]

renovatebot/base-image#3183

Once released, and bumped in Renovate itself, then you'll be unblocked!

[jamietanna]

Resolved in 43.244.0