QNX builds fail inside DevContainer due to missing license and user setup

[dcalavrezo-qorix]

Context

We are currently using a DevContainer for development, but QNX builds within Bazel fail because the environment is not properly configured for QNX licensing and user credentials.

In the CI build (which works correctly), the following environment variables are set and used to install the QNX license:

env:
  SCORE_QNX_LICENSE: ${{ secrets.SCORE_QNX_LICENSE }}
  SCORE_QNX_USER: ${{ secrets.SCORE_QNX_USER }}
  SCORE_QNX_PASSWORD: ${{ secrets.SCORE_QNX_PASSWORD }}

run: |
  mkdir -p /opt/score_qnx/license
  echo "${SCORE_QNX_LICENSE}" | base64 --decode > /opt/score_qnx/license/licenses

Problem Details

• In the DevContainer, these environment variables are not set by default.

The QNX license file needs to exist at: /opt/score_qnx/license/licenses

• The current username inside the DevContainer is always vscode, not the actual system username — which might cause mismatches when setting up license paths or user-specific configurations.

What we need

We need a convenient and secure way to:

Make the QNX license and credentials available inside the DevContainer (e.g. via environment variables or a mounted secret file).

Ensure that /opt/score_qnx/license/licenses is created and populated correctly.

Handle the username mismatch between the local user and vscode inside the container.