Managing watsonx Orchestrate Developer Edition server
After you install the watsonx Orchestrate server, you manage the local watsonx Orchestrate Developer Edition server using the ADK CLI. With the CLI, you stop or start the server, reset it, view container logs, and manage the VM that hosts the containers. You can attach or release the VM, edit its settings, or log in using SSH.
The username you configure for watsonx Orchestrate Developer Edition services. If you do not provide a username, the system generates one by using your OS username. If that attempt fails, the system sets the name orchestrate. This applies to Langfuse, Minio, MCP Gateway, and ClickHouse. The username must contain at least three characters.
Note:For users who update from earlier versions to 2.6.0. If you have any server configured by an older version, whether it is running or stopped, your database uses the old default credentials because the database was created before the new configuration. You need to reset and start the environment to ensure the database container uses the newest credentials.If you want to keep your existing data after the update, you can override the service credentials for each service by configuring them in the .env file. For more information, see the related documentation section. For more information, see Configure services credentials for watsonx Orchestrate Developer Edition in the .env file.
The password you configure for watsonx Orchestrate Developer Edition services. If you do not provide a password, the system prompts you to enter one during the first setup. This applies to PostgreSQL, Langfuse, Minio, MCP Gateway, ElasticSearch, Milvus, and Clickhouse. The password must contain at least eighteen characters.
Note:For users who update from earlier versions to 2.6.0. If you have any server configured by an older version, whether it is running or stopped, your database uses the old default credentials because the database was created before the new configuration. You need to reset and start the environment to ensure the database container uses the newest credentials.If you want to keep your existing data after the update, you can override the service credentials for each service by configuring them in the .env file. For more information, see the related documentation section. For more information, see Configure services credentials for watsonx Orchestrate Developer Edition in the .env file.
Resetting watsonx Orchestrate Developer Edition server
Reset the environment instead of uninstalling and reinstalling. This command stops the server, removes all Docker containers, and clears data volumes. Use it when you need a clean environment for development. Run:
The installation creates a VM named ibm-watsonx-orchestrate that hosts the watsonx Orchestrate Developer Edition containers. By default, the VM uses 8 cores and 16 GB RAM. You can change CPU, memory, and disk space to improve performance or fit your hardware limits. Run:
Note:You cannot edit disks for VMs running in WSL.
BASH
orchestrate server edit --cpus <cpu-cores> --memory <memory> --disk <disk-space>
Attaching watsonx Orchestrate Developer Edition to a Docker engine
The installation creates a VM named ibm-watsonx-orchestrate that hosts the watsonx Orchestrate Developer Edition containers. Attach Docker to this VM context when you need Docker commands to run inside the VM instead of your local machine. This is useful if you want to manage containers that belong to the watsonx Orchestrate environment directly. Run:
Logging into watsonx Orchestrate Developer Edition VM using SSH
The installation creates a VM named ibm-watsonx-orchestrate that hosts the watsonx Orchestrate Developer Edition containers. Access this VM with SSH when you need direct control. Run:
