This repository defines an example of a Docker extension. The files in this repository have been automatically generated as a result of running docker extension init.
This extension is composed of:
- A frontend app in React that makes a request to the
/helloendpoint and displays the payload in Docker Desktop. - A backend container that runs an API in Go. It exposes the
/helloendpoint which returns a JSON payload.
You can build your Docker Extension using your fav tech stack:
- Frontend: React, Angular, Vue, Svelte, etc. Basically, any frontend framework you can bundle in an
index.htmlfile with CSS, and JS assets.- Backend (optional): anything that can run in a container.
Looking for more templates?
Request one or submit yours here.
You can use docker to build, install and push your extension. Also, we provide an opinionated Makefile that could be convenient for you. There isn't a strong preference of using one over the other, so just use the one you're most comfortable with.
To build the extension, use make build-extension or:
docker buildx build -t my/awesome-extension:latest . --loadTo install the extension, use make install-extension or:
docker extension install my/awesome-extension:latestIf you want to automate this command, use the
-for--forceflag to accept the warning message.
To preview the extension in Docker Desktop, open Docker Dashboard once the installation is complete. The left-hand menu displays a new tab with the name of your extension. You can also use docker extension ls to see that the extension has been installed successfully.
During the development of the frontend part, 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. Assuming your app runs on the default port, start your UI app and then run:
cd ui
npm install
npm run devThis 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:
docker extension dev ui-source my/awesome-extension:latest http://localhost:3000In order to open the Chrome Dev Tools for your extension when you click on the extension tab, run:
docker extension dev debug my/awesome-extension:latestEach subsequent click on the extension tab will also open Chrome Dev Tools. To stop this behaviour, run:
docker extension dev reset my/awesome-extension:latestThis example defines an API in Go that is deployed as a backend container when the extension is installed. This backend could be implemented in any language, as it runs inside a container. The extension frameworks provides connectivity from the extension UI to a socket that the backend has to connect to on the server side.
Note that an extension doesn't necessarily need a backend container, but in this example we include one for teaching purposes.
Whenever you make changes in the backend source code, you will need to compile them and re-deploy a new version of your backend container.
Use the docker extension update command to remove and re-install the extension automatically:
docker extension update my/awesome-extension:latestIf you want to automate this command, use the
-for--forceflag to accept the warning message.
Extension containers are hidden from the Docker Dashboard by default. You can change this in Settings > Extensions > Show Docker Extensions system containers.
To remove the extension:
docker extension rm my/awesome-extension:latest- To learn more about how to build your extension refer to the Extension SDK docs at https://docs.docker.com/desktop/extensions-sdk/.
- To publish your extension in the Marketplace visit https://www.docker.com/products/extensions/submissions/.
- To report issues and feedback visit https://github.com/docker/extensions-sdk/issues.
- To look for other ideas of new extensions, or propose new ideas of extensions you would like to see, visit https://github.com/docker/extension-ideas/discussions.