Rpm packages


The Rpm Update Module updates software on the device using the native local package manager.

A Mender Artifact containing one or more software packages is send to the device, where the Update Module will call the package manager to install them in alphabetical order.


Module name rpm
Supports rollback no
Requires restart no
Artifact generation script no
Full operating system updater no
Source code Update Module
Maintainer Community

Please be aware that Mender Update modules are meant to update parts of the operating system and if not configured properly they could potentially delete parts or the complete operating system. Always inspect the code carefully and only test modules on a device that you can recover easily.

It is not recommended to install a Mender Artifact on your workstation

Prepare the device

This section describes how to setup your target device, i.e. the device to be updated. This will also be referred to as the device environment.

All commands outlined in this section should be run in the device environment.


This update module has the following prerequisites for the device environment:

Install the Update Module

Download the latest version of this Update Module by running:

mkdir -p /usr/share/mender/modules/v3 && wget -P /usr/share/mender/modules/v3 https://raw.githubusercontent.com/mendersoftware/mender/master/support/modules/rpm

Prepare the development environment on your workstation

This section describes how to set up your development environment on your workstation.

All commands outlined in this section should be run in the development environment.


This Update Module has the following prerequisites for the development environment:

Create Mender Artifacts

The Artifact can be generated using the mender-artifact tool.

Now generate a Mender Artifact using the following command:

PACKAGES="my-package-1.rpm my-package-2.rpm"
mender-artifact write module-image -T rpm -n ${ARTIFACT_NAME} -t ${DEVICE_TYPE} -o ${OUTPUT_PATH} -f $(echo "$PACKAGES" | sed -e 's/ / -f /g')
  • ARTIFACT_NAME - The name of the Mender Artifact
  • DEVICE_TYPE - The compatible device type of this Mender Artifact
  • OUTPUT_PATH - The path where to place the output Mender Artifact. This should always have a .mender suffix
  • PACKAGES - List of all .rpm packages to be contained in the Artifact.

You can either deploy this Artifact in managed mode with the Mender server (upload it under Releases in the server UI) or by using the Mender client only in Standalone deployments.

Artifact technical details

The Mender Artifact used by this Update Module has a payload with as many files as software packages we are sending in the Artifact.

Example of a rpm Update Module Artifact with two packages will look like:

Mender artifact:
  Name: my-update-1.0
  Format: mender
  Version: 3
  Signature: no signature
  Compatible devices: '[my-device-type]'
  Provides group: 
  Depends on one of artifact(s): []
  Depends on one of group(s): []
  State scripts:

    Type:   rpm
    Provides: Nothing
    Depends: Nothing
    Metadata: Nothing
      name:     my-package-1.rpm
      size:     0
      modified: 2019-04-15 11:27:10 +0200 CEST
      checksum: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
      name:     my-package-2.rpm
      size:     0
      modified: 2019-04-15 11:27:12 +0200 CEST
      checksum: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b85
1 Like