Skip to content

DLC Installation with dlc_install

The dlc_install command in the ChromeOS Shell enables users to trigger the installation of DLCs (Downloadable Content) for testing purposes. This command interacts with a test update server, which may deliver unverified content.

Warning

  • Test Environment: The DLCs served by the test update server are signed for verification purposes but may not be intended for general use.
  • Risk of Failure: Installations will fail if the DLC payloads are not properly signed or verifiable.

Usage

Trigger a DLC installation using the following command:

dlc_install <dlc-id>

Replace <dlc-id> with the identifier of the DLC to be installed.

Example

# Install a DLC with the ID "example-dlc"
dlc_install example-dlc

Additional Information

  • Interaction with Update Engine: The dlc_install command passes the special string autest to the update engine, ensuring that requests target the QA Omaha server rather than the production server.

  • Signed Payloads: Only DLC payloads that are signed and verifiable can be successfully installed.

Best Practices

  1. Test Environment Only

  2. Use this command strictly in testing environments to avoid unintended consequences.

  3. Verify Payloads

  4. Ensure DLC payloads are properly signed and verified before triggering installations.

  5. Monitor Installations

  6. Check logs to verify successful installation or diagnose potential failures.

This tool is essential for developers aiming to test and validate DLC installations in controlled environments.