Dev Containers: stack-up-iot-manager Command

Deployment
,
1

I am up and running with the CM-provided image for my dev container. I noticed that VS Code has some command buttons along that bottom that are unique to CM customization development. These include:

  • cmf login
  • stack-up
  • stack-up-iot-manager
  • stack-up-data-platform
  • stack-down
  • stack-down-remove-volumes

I can see that these correspond to tasks defined in the “.vscode/tasks.json” file. Of particular interest to me is the stack-up-iot-manager task. When I execute it, I am prompted for a manager name, which I provide. The resulting command is this:

npx --yes cross-env CONNECT_IOT_MANAGER_NAME=‘’ cmf dev local stack up -c .localenv/iotmanager -c .localenv/iotmanager/custom-volumes --docker-progress auto

Where is the name of an IoT manager that I was prompted for when executing the command.

The result is below. Clearly, I’m missing something with the “custom-volumes” directory or file. I can’t find documentation on this and was would like to know what this command does and how to make sure my environment is set up correctly to use it.
Executing task: npx --yes cross-env CONNECT_IOT_MANAGER_NAME=‘my-iot-manager’ cmf dev local stack up -c .localenv/iotmanager -c .localenv/iotmanager/custom-volumes --docker-progress auto

Could not retrieve latest version information. Try again later.
Some components were not found:
Component .localenv/iotmanager/custom-volumes not found in /workspaces/mes

dev local stack up -c .localenv/iotmanager -c .localenv/iotmanager/custom-volumes --docker-progress auto did not finished successfully.

2

Hello,

I experienced the same issue. If it hasn’t already been resolved, I’ll leave the solution here in case it helps others.

I believe the tasks file is a bit outdated. The custom-volumes configuration is used to set up the volumes required by the IoT Manager (for example, the file driver). However, these volumes can be defined directly in the main IoT Manager Docker Compose file.

Therefore, the following parameter can be removed:

-c .localenv/iotmanager/custom-volumes

After removing it, the deployment should work as expected.

Best regards