Torizon IDE extension - docker registry password entry

Technical Support
1

Hi,

after the latest version 3.4.0 of the VS Code extension was installed, the ‘create-production-image’ task always asks for the docker registry password. Then the entry in settings.json gets overwritten. Is it possible to suppress this feature and skip the password query? I already have a correct password in settings.json.

I also tried to fill the Docker_password User setting of the extension, but it kept asking for the password anyway. I think the extension should not ask for the password if it finds it in the settings.

Meanwhile I reverted to the version 3.3.0 of the extension.

Thank you for your support.

EDIT: I figured out that I need to set for all tasks
“DOCKER_PASSWORD”: “${config:docker_password}”,

This solved the issue in our setup.

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

Based on the Torizon IDE Extension documentation, your solution is correct. The docker_password property is designed to be stored securely and reused across task runs.

How docker_password Works

According to the documentation, the docker_password property is set by the extension when you’re first asked for the DockerHub password during the initial run of the create-production-image task(1). The value secret indicates that the real value is stored in the VS Code vault(1).

The property is designed so that “the value then is used in the next runs of the task. If you want to change the password, you can remove the property or set it to an empty string, then the extension will ask for the password again in the next run of the task”(1).

Your Solution

Your workaround of setting:

"DOCKER_PASSWORD": "${config:docker_password}"

is the correct approach for referencing the stored password in task configurations(1).

Security Note

The documentation includes an important warning about credential handling: “When using a VS Code integrated terminal, your Docker password credentials will be passed as environment variables. Avoid running commands that print or export the environment (e.g., env, set, printenv) to prevent credential leaks”(1).

Alternative Approach

If you continue experiencing issues with password prompts, you can manually manage the docker_password setting in your .vscode/settings.json file. If you set it to an empty string or remove it entirely, the extension will prompt for the password again on the next task run(1).

The behavior you experienced with version 3.4.0 asking for the password despite having it configured suggests there may have been a change in how the extension handles the stored credentials between versions.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.