Test and debug (original) (raw)

In order to improve the developer experience, Docker Desktop provides a set of tools to help you test and debug your extension.

Open Chrome DevTools

In order to open the Chrome DevTools for your extension when you select the Extensions tab, run:

Each subsequent click on the extension tab also opens Chrome DevTools. To stop this behaviour, run:

After an extension is deployed, it is also possible to open Chrome DevTools from the UI extension part using a variation of theKonami Code. Select the Extensions tab, and then hit the key sequence up, up, down, down, left, right, left, right, p, d, t.

Hot reloading whilst developing the UI

During UI development, it’s helpful to use hot reloading to test your changes without rebuilding your entire extension. To do this, you can configure Docker Desktop to load your UI from a development server, such as the oneVite starts when invoked with npm start.

Assuming your app runs on the default port, start your UI app and then run:

This starts a development server that listens on port 3000.

You can now tell Docker Desktop to use this as the frontend source. In another terminal run:

Close and reopen the Docker Desktop dashboard and go to your extension. All the changes to the frontend code are immediately visible.

Once finished, you can reset the extension configuration to the original settings. This will also reset opening Chrome DevTools if you used docker extension dev debug <name-of-your-extensions>:

If your extension is composed of one or more services running as containers in the Docker Desktop VM, you can access them easily from the dashboard in Docker Desktop.

  1. In Docker Desktop, navigate to Settings.
  2. Under the Extensions tab, select the Show Docker Desktop Extensions system containers option. You can now view your extension containers and their logs.

To remove the extension, run: