Issues with Docker Update Module

lluiscampos · April 3, 2019, 7:14am

Hi @Prakash and welcome to Mender Hub!

As it is, this Update Module does not support passing arguments to the container. However, it is pretty easy to create a new module based on this one that could achieve that.

Have a look at the Docker Update Module and generator source code (links in table above) for inspiration. One possibility could be to pass the parameters as an extra field in the meta-data contained in the Mender Artifact.

ramu · May 22, 2019, 7:05am

Hi IIuiscampos
I am trying build mender artifact for hello-world docker image…
ARTIFACT_NAME=“my-container-update-1.0”
DEVICE_TYPE=“solidrun”
OUTPUT_PATH=my-container-update-1.0.mender
DOCKER_IMAGES=“hello-world”
Hope my DOCKER_IMAGES is correct…

./docker-artifact-gen -n {ARTIFACT_NAME} -t {DEVICE_TYPE} -o {OUTPUT_PATH} {DOCKER_IMAGES}
Using default tag: latest
latest: Pulling from library/hello-world
Digest: sha256:6f744a2005b12a704d2608d8070a494ad1145636eeb74a570c56b94d94ccdbfc
Status: Image is up to date for hello-world:latest
No help topic for 'module-image’
I see meta-data.json only in my directory

kacf · May 22, 2019, 7:39am

Are you using the latest mender-artifact tool v3.0.0? Make sure you
download the latest one from
https://docs.mender.io/2.0/artifacts/modifying-a-mender-artifact#prerequisites
and install it in your path.

ramu · May 22, 2019, 9:48am

Thank you… Now ./docker-artifact-gen able to create the my-container-update-1.0.mender…

ramu · May 22, 2019, 10:09am

Mender Management server for production throwing following error, When i was trying to upload the Artifact…
Seems to be My mender server not supporting version 3…

Artifact couldn’t be uploaded. unsupported version: 3; supported versions are: 1, 2 [Request ID: 3f00876f]

mirzak · May 22, 2019, 12:12pm

Looks like you are not running 2.0.0 version of the server.

ramu · May 23, 2019, 1:05pm

My Mender Server version : 2.0
Mender-artifact tool version : 3.0
I created the mender artifact for Hello-world docker image with Mender-artifact 3.0 tool. But when I want to deploy above docker image to device, mender client on the device throwing below error. I think there is version mismatch …
My meta-mender version is thud-v2019.02-4-gdb6b761

May 23 12:54:37 imx6 mender[743]: level=error msg=“update install failed: installer: failed to read and install update: reader: unsupported version: 3” module=state
May 23 12:54:37 imx6 mender[743]: level=info msg=“State transition: update-store [Download] -> fetch-install-retry-wait [Download]” module=mender

mirzak · May 23, 2019, 1:08pm

It seems that you are not running Mender client 2.0.0,

It is not the default and you have to actively enable that version, take a look here

https://hub.mender.io/t/mender-2-0-released-extending-update-capability/536/15

for more information

ramu · May 24, 2019, 5:07pm

I updated thud branch and now the version is thud-v2019.05-2-gae00ee7 and added below stuff in local.conf and i see mender_client 2.0.0 in logs from my device…

PREFERRED_VERSION_pn-mender = "2.%"
PREFERRED_VERSION_pn-mender-artifact = "3.%"
PREFERRED_VERSION_pn-mender-artifact-native = "3.%"

Now I created mender artifact for hello-world docker and uploaded this artifact i.e my-container-update-1.0 into server.This artifact size is 6kb and showing its type as rootfs-image in the server.
Downloaded the docker updated module in device @ /usr/share/mender/modules/v3.
After downloading this artifact into device, the device is getting rebooted and inventory shows current software as my-container-update-1.0.

ramu · May 31, 2019, 6:16am

Why the board is rebooting when we download the application software image on to device?

mirzak · May 31, 2019, 7:51am

Why the board is rebooting when we download the application software image on to device?

Unclear, the Docker update module does not do a reboot, is it possible that it is triggered by something else?

ramu · June 3, 2019, 6:58am

Hope below steps i followed are correct… Initially my docker is not running on the board and board have a /usr/share/module/v3/docker script…

I have created mender artifact for hello-world docker and uploaded this artifact i.e my-container-update-1.0 into server.This artifact size is 6kb and showing its type as rootfs-image in the server.
Downloaded the docker updated module in device @ /usr/share/mender/modules/v3.
After downloading this artifact into device, the device is getting rebooted and inventory data on the server shows current software as my-container-update-1.0

lluiscampos · June 3, 2019, 8:50am

Hi @ramu,

How are you creating the Artifact? Using the docker-artifact-get script the resulting Artifact must be module-image, not rootfs-image. Can you copy here the commands you are using to create the Artifact?

I think that somehow you are creating a rootfs-image Artifact probably containing only the Docker metadata (6kb?), but then the device will try to install it as if it was an actual full image update.

ramu · June 3, 2019, 9:03am

Exported below stuff…
ARTIFACT_NAME=“my-container-update-1.0”
DEVICE_TYPE=“imx6”
OUTPUT_PATH=my-container-update-1.0.mender
DOCKER_IMAGES=“hello-world”

./docker-artifact-gen -n {ARTIFACT_NAME} -t {DEVICE_TYPE} -o {OUTPUT_PATH} {DOCKER_IMAGES}
Using default tag: latest
latest: Pulling from library/hello-world
Digest: sha256:6f744a2005b12a704d2608d8070a494ad1145636eeb74a570c56b94d94ccdbfc
Status: Image is up to date for hello-world:latest

lluiscampos · June 3, 2019, 9:13am

Thanks. Okey, so what is the output of: mender-artifact read my-container-update-1.0.mender ? It cannot be rootfs-image.

ramu · June 3, 2019, 9:20am

Iam seeing type as “rootfs-image” under “Releases” link on the mender server page running on my laptop…

Here is the o/p of "mender-artifact read " …

~/workspace/mender/mender-artifact read my-container-update-1.0.mender
Mender artifact:
  Name: my-container-update-1.0
  Format: mender
  Version: 3
  Signature: no signature
  Compatible devices: '[tcs-imx6]'
  Provides group: 
  Depends on one of artifact(s): []
  Depends on one of group(s): []
  State scripts:

Updates:
    0:
    Type:   docker
    Provides: Nothing
    Depends: Nothing
    Metadata:
	{
	  "containers": [
	    "hello-world@sha256:6f744a2005b12a704d2608d8070a494ad1145636eeb74a570c56b94d94ccdbfc"
	  ]
	}

But signed mender artifact giving following o/p …

~/workspace/mender/mender-artifact read my-container-update-1.0-sign.mender 
Mender artifact:
  Name: my-container-update-1.0
  Format: mender
  Version: 3
  Signature: signed; verification using provided key failed
  Compatible devices: '[tcs-imx6]'
  Provides group: 
  Depends on one of artifact(s): []
  Depends on one of group(s): []
  State scripts:

Updates:
    0:
    **Type:   rootfs-image**
    Provides: Nothing
    Depends: Nothing
    Metadata: Nothing
    Files:
      name:     mender-repack287398683
      size:     0
      modified: 2019-05-22 15:31:52 +0530 IST
      checksum: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

Edit: @mirzak: prettify output

lluiscampos · June 3, 2019, 12:08pm

Okey! Now I understand it.

We have a bug that does not allow signing module-image artifacts, see MEN-2573. Try this workaround suggested by @kacf .

ramu · June 4, 2019, 7:03am

Thank you…
I have tried with out signing the mender articraft for hello-world docker… Now Docker Update module
able to download and start the docker. But mender server showing the current software for device as
my-container-update-1.0 (This is docker release) …

I will try with signed one now…

lluiscampos · June 4, 2019, 8:52am

That is expected. The “current software” reports the last Artifact installed in the device.

ramu · June 4, 2019, 9:05am

But it suppose to show the rootfs-image version right??

Topic		Replies	Views
Docker Update Modules docker	19	12459	May 19, 2023
Suggestion: add a skip-images option to app-update-module General Discussions	1	13	October 25, 2024
Create an update for a Docker Image General Discussions	4	914	May 10, 2024
Docker-compose images in GitHub CI/CD General Discussions docker , update-modules	4	115	April 9, 2024
Deploying offline Docker Images on devices within private networks? General Discussions	3	377	July 4, 2022

Issues with Docker Update Module

Related topics