VC fails to start on 1.0.17 with custom graffiti

[emizzle]

Describe the bug

On version 1.0.17, setting a custom graffiti causes the validator client to stop working, with the error nimbus_validator_client does not accept arguments .

I noticed that my validator stopped attesting after an auto update, and eventually reinstalled the nimbus dappnode package, which reset my graffiti to default. This solved the initial problem, but after re-updating my graffiti, the problem returned.

To Reproduce

Steps to reproduce the behavior:

1. Set custom graffiti
2. Auto update to 1.0.17

Expected behavior

Custom graffiti should be allowed and validator client should continue to validate as per 1.0.16.

Actual behavior

VC fails to start with nimbus_validator_client does not accept arguments

Screenshots

DAppNode version:

Core DAppNode Packages versions
bind.dnp.dappnode.eth: 0.2.11
core.dnp.dappnode.eth: 0.2.103
dappmanager.dnp.dappnode.eth: 0.2.97, commit: 2e87643b
https.dnp.dappnode.eth: 0.2.2
ipfs.dnp.dappnode.eth: 0.2.23
wifi.dnp.dappnode.eth: 0.2.9
wireguard.dnp.dappnode.eth: 0.1.3

System info
dockerComposeVersion: 2.24.2
dockerServerVersion: 20.10.24+dfsg1
dockerCliVersion: 20.10.24+dfsg1
os: debian
versionCodename: bookworm
architecture: amd64
kernel: 6.1.0-15-amd64
Disk usage: 79%

• Package version: 1.0.17 (status-im/nimbus-eth2@v25.2.0, dappnode/staker-package-scripts@v0.1.1 upstream)
• OS: DappNode core v.0.2.103

Additional context

[emizzle]

I originally solved my issue using these steps, but later figured out that it's actually the custom graffiti setting that causes the issue:

1. Deleting the Nimbus package, but keeping the data dir (screenshots 1, 2)
2. Re-selecting Nimbus from the Stakers UI, then applying the changes (screenshot 3)