@@ -9,22 +9,22 @@ run it interactively, perhaps to help diagnose a problem.
99
1010Docker images are automatically published to:
1111
12- - https://hub.docker.com/r/jpmens/mqttwarn
1312- https://github.com/orgs/jpmens/packages/container/package/mqttwarn-standard
1413- https://github.com/orgs/jpmens/packages/container/package/mqttwarn-full
14+ - ~~ https://hub.docker.com/r/jpmens/mqttwarn ~~ (not automatically updated)
1515
1616## Choosing the Docker image
1717
1818Choose one of those Docker images.
1919``` shell
20- # The standard image on Docker Hub.
21- export IMAGE=jpmens/mqttwarn
22-
2320# The standard image on GHCR.
2421export IMAGE=ghcr.io/jpmens/mqttwarn-standard:latest
2522
2623# The full image on GHCR.
2724export IMAGE=ghcr.io/jpmens/mqttwarn-full:latest
25+
26+ # The standard image on Docker Hub.
27+ export IMAGE=jpmens/mqttwarn
2828```
2929
3030## Interactively
@@ -157,7 +157,7 @@ images.
157157
158158In order to use ` mqttwarn ` with additional Python modules not included in the
159159baseline image, you will need to build custom Docker images based on the
160- canonical ` jpmens/mqttwarn ` .
160+ canonical ` ghcr.io/ jpmens/mqttwarn-standard:latest ` .
161161
162162We prepared an example which outlines how this would work with the Slack SDK.
163163By using the ` Dockerfile.mqttwarn-slack ` , this command will build a Docker
@@ -166,3 +166,11 @@ image called `mqttwarn-slack`, which includes the Slack SDK:
166166``` shell
167167docker build --tag=mqttwarn-slack --file=Dockerfile.mqttwarn-slack .
168168```
169+
170+ ## The "full" image, including all dependencies
171+
172+ If you prefer not to fiddle with those details, but instead want to run a full
173+ image including dependencies for all modules, we have you covered. Alongside
174+ the standard image, there is also ` ghcr.io/jpmens/mqttwarn-full:latest ` .
175+
176+ The ` standard ` image weighs in with about 130 MB, the ` full ` image has 230 MB.
0 commit comments