Issue running 'service rusk start' on local setup

[kenrickl]

Describe the bug Issue running service rusk start on a local setup.

To Reproduce

1. first installed latest stable ITN release through curl
2. configured rusk-wallet and exported consensus keys (had to manually open permissions to /opt through sudo chmod 775 /opt and sudo chown -R $USER:$USER /opt/dusk
3. set consensus pw successfully through /opt/dusk/bin/setup_consensus_pwd.sh
4. start rusk through service rusk start

Expected behaviour expected node to start syncing after starting rusk service.

Logs/Screenshot the logs of rusk (through tail -F /var/log/rusk.log) shows repeatedly:

Using CONSENSUS_KEYS in /opt/dusk/conf/consensus.keys
2024-02-16T15:32:51.206596Z  INFO rusk: Using state from "/opt/dusk/rusk/state"
2024-02-16T15:32:51.208971Z  INFO rusk: Rusk VM loaded
2024-02-16T15:32:51.209073Z  INFO node::databroker: DataBrokerSrv::new with conf: max_inv_entries: 100, max_ongoing_requests: 1000
2024-02-16T15:32:51.209113Z  INFO node::database::rocksdb: Opening database in "/opt/dusk/rusk/chain.db"

error logs through cat /var/log/rusk.err:

thread 'main' panicked at /home/docker/actions-runner/_work/rusk/ruskthread 'main' panicked at /home/docker/actions-runner/_work/rusk/ruskthread 'main' panicked at /home/docker/actions-runner/_work/rusk/rusk/node/src/database/rocksdb.rs:164:18:
should be a valid database in {path}: Error { message: "Failed to create RocksDB directory: `Os { code: 13, kind: PermissionDenied, message: \"Permission denied\" }`." }

Platform

• Architecture: ARM
• OS: Ubuntu 22.04.3 LTS
• ITN installer: both v0.1.0 and latest version show similar issue

Additional context Add any other context about the problem here.