edgexfoundry/device-mqtt-arm64 repository overview

⁠Quick reference

• Maintained by: EdgeX Foundry⁠ (a Linux Foundation⁠ project)

• Where to get help: EdgeX Web Site⁠, EdgeX Documentation⁠, EdgeX Slack⁠, EdgeX Project Wiki⁠

⁠Supported tags and respective Dockerfile links

• Napa
  • 3.1.0 - Dockerfile⁠
• Minnesota
  • 3.0.0 - Dockerfile⁠
• Levski
  • 2.3.0 - Dockerfile⁠
• Kamakura
  • 2.2.0 - Dockerfile⁠
• Jakarta (LTS⁠)
  • 2.1.0 - Dockerfile⁠
• Ireland
  • 2.0.0 - Dockerfile⁠

⁠Quick reference

• Where to file issues: https://github.com/edgexfoundry/device-mqtt-go/issues⁠
• Supported architectures: arm64
• Source of this description: https://github.com/edgexfoundry/cd-management/tree/edgex-docker-hub-documentation/image-overview-templates/new-names/device-mqtt-arm64.md⁠

⁠What is EdgeX Foundry?

EdgeX Foundry is a vendor-neutral, open source project hosted by The Linux Foundation building a common open framework for IoT edge computing. At the heart of the project is an interoperability framework hosted within a full hardware and OS agnostic reference software platform to enable an ecosystem of plug-and-play components that unifies the marketplace and accelerates the deployment of IoT solutions.

In simple terms, EdgeX is edge middleware - serving between physical sensing and actuating "things" and our information technology (IT) systems.

EdgeX's official documentation can be found at docs.edgexfoundry.org⁠.

Edgey - the official EdgeX Foundry project mascot

⁠What's in this image?

This image contains the ARM64 version of the MQTT device service, for connecting a MQTT topic to EdgeX acting like a device/sensor feed.

The device MQTT service source code: https://github.com/edgexfoundry/device-mqtt-go⁠

⁠License

View license information⁠ for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

Some additional license information which was able to be auto-detected might be found in the Attribution.txt file located in the image and copied from the associated