-
Type:
Task
-
Status: Done
-
Priority:
(None)
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:
-
Epic Link:
Converting Raspberry Pi 3 images seem to work fine in the mender-convert container environment - I tested a conversion and OTA update end-to-end for the Raspberrry Pi.
However, when converting a BeagleBone image (9.5 Debian) inside this container, the following message is printed:
mount: /mender-convert/output/embedded/rootfs: WARNING: device write-protected, mounted read-only.
The resulting .sdimg does boot and connect to the Mender server correctly. However there seems to be something wrong with the resulting Artifact, as `mender-artifact` generates an error message when working with it (modify --name).
Steps to reproduce:
Follow instructions in https://github.com/mendersoftware/mender-convert/blob/master/docker/README.md.
However, instead of Raspbian / raspberry in Use the mender-convert container image, use this configuration:
Image: https://debian.beagleboard.org/images/bone-debian-9.5-iot-armhf-2018-10-07-4gb.img.xz
DEVICE_TYPE="beaglebone"
RAW_DISK_IMAGE="input/bone-debian-9.5-iot-armhf-2018-10-07-4gb.img"
MENDER_CLIENT="input/mender-1.7.0b1-arm-linux-gnueabihf-gcc"
ARTIFACT_NAME="bone-debian-9.5-iot-armhf-2018-10-07"
MENDER_DISK_IMAGE="bone-debian-9.5-iot-armhf-2018-10-07.sdimg"
TENANT_TOKEN="<COPY-FROM https://hosted.mender.io/ui/#/settings/my-organization>"
./mender-convert from-raw-disk-image \
--raw-disk-image $RAW_DISK_IMAGE \
--mender-disk-image $MENDER_DISK_IMAGE \
--device-type $DEVICE_TYPE \
--mender-client $MENDER_CLIENT \
--artifact-name $ARTIFACT_NAME \
--bootloader-toolchain arm-linux-gnueabihf \
--server-url "https://hosted.mender.io" \
--tenant-token $TENANT_TOKEN
- relates to
-
-
- Done
-
