This can be used for local config settings intended to override the defaults in
configs/
Signed-off-by: Drew Moseley <drew.moseley@northern.tech>
Changelog: Title
It was pointing to a resource on mender.io, which duo to recent
website updates was moved/removed.
Update the URL to use the logo that is present in mendersoftware/mender,
which hopefully will not move as much.
Changelog: None
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
The goals of the re-write was to achieve the following:
1. It should be easy to extend the tool to support other boards or distributions
2. We should not compile code in the tool (rely on binaries built elsewhere)
compiling code increases complexity, due to requirement of toolchains etc.
3. The tool shall not be designed around specific hardware/platform types
- This is the case today with the usage of --device-type flag
4 The tool should be to convert images without knowing anything about the hardware/platform
relates to above 3.
5. Configuration interface should be simplified
- command line flags -> configuration files
6. Platform specific code shall be provided trough “hooks”, and are not part of the “core” mender-convert code
7. It shall be easy to extend functionality
- support for rootfs overlay to inject user applications/configurations
- ability to override how the Mender Artifact is generated (to be able to sign and include state-scripts)
8. Code structure should be modular
- Eases Maintenance and possibility of making isolated changes
Changelog: Title
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
Use losetup's automatic allocation mode to atomically find and allocate loop devices. This should make mender-convert safer to use concurrently with itself and other applications allocating loop devices.
Changelog: Title
Signed-off-by: Simon Guigui <fyhertz@gmail.com>
Current stable version 3.0.x should be the transition, as for future
versions we will be releasing the binary in a linux/darwin folder.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
So there are other arguments that need to be passed to docker build,
namely toolchain related, therefore it is better to use the default
script and just override the image name.
Also, removing the Mender version from the GitLab pipeline (and hence
using the one defined in build-docker) removes one point of
inconsistency.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
This file needs to be present for state-scripts to work as the format
version will be validated using the information provided in this file
and the version in the Mender Artifact.
"3" means that it will only accept state-scripts created using
Mender Artifact version 3.
Changelog: Title
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
Currently the code expands to the following in mender.conf:
/mender-convert/output/sdimg/primary/etc/mender/server.crt
${primary_dir} should be dropped from assignment
Fixes: d5e861b052 ("add ServerCertificate entry in mender.conf if servert.crt was installed")
Changelog: None
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
MEN-2640
Changelog: Title
Based on work from:
Signed-off-by: Yevgeniy Nurseitov <enurseitov@gmail.com>
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
--demo-host-ip/-i would imply that the intention is to use the
demo server, otherwise we do not not want to install the demo
certificate.
Changelog: Title
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
It seems some additional manipulation was added to cmdline.txt in the upstream
init_resize.sh script, the part that removed the 'quiet' kernel argument is what
will add the Linux kernel console on HDMI again and if 'quiet' is present nothing is
shown on the HDMI output resulting in a "black screen".
MEN-2673
Changelog: Fix console not being available on HDMI on Raspberry Pi in Raspbian Buster.
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
The changes applied here deviate from the Raspbian environment and
will change behaviour. These are not necessary for the Mender
integration to work and are mostly for "convenience" and for this
reason we drop them to stay as close to possible to the Raspbian
environment.
Changelog: None
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
Changelog: None
Signed-off-by: Mario Kozjak <kozjakm1@gmail.com>
device-image-shell: qemu-user-static info
Signed-off-by: Mario Kozjak <kozjakm1@gmail.com>
Note that this integration relies on an "standard" U-boot integration,
but the binaries are not built in mender-convert and instead it
relies on fetching pre-built binaries.
Changelog: Support for RockPro64 board
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
So far the assumption has been that we are targeting an arm (32-bit),
when we are compiling the Mender client during docker container build.
To be able to support other platfors we need to parameterize this, and
this commit adds support for arm64.
Changelog: Title
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
Changelog: Since mender-convert now automatically resizes the input image, there is an additional step that is executed.
Signed-off-by: Simon Ensslen <simon.ensslen@griesser.ch>
Changelog: Instruct U-Boot to be able to boot either a compressed or an uncompressed kernel. This is very useful e.g. when switching from Debian (Raspbian) created using mender-convert to a Yocto based environment that does not compress the Kernel by default.
Signed-off-by: Simon Ensslen <simon.ensslen@griesser.ch>
That is if it fails, proceed with conversion without it.
The current logic only supports shrinking a rootfs on BBB and RPi
devices (this is deducted from $raw_disk_counts) and calling
'disk_image_shrink_rootfs' would fail on 'qemux86_64' device.
Shrinking the rootfs is not a hard-requirement and is only an
optimization (mainly for RPi devices).
Changelog: None
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
This message has lately generated some confusion,
*** Data partition size set to default value: 128MB ***
1/9 Repartitioning raw disk image...
Detected raw disk image with 2 partition(s).
Calculating partitions' sizes of the Mender image.
Adjust Mender disk image size to the total storage size (2048MB).
Defined total storage size of MB is too small.
Minimal required storage is 60056MB. Aborting.
There are two things here that are hard to understand:
- Why does it not respect the 'storage-total-size-mb' setting of 2048MB?
- Where does the 60GB requirement come frome?
This normally happens if you have booted an image once on e.g Raspbian,
which will expand the rootfs to occupy the reamining blocks of the SD
card. And if you then do a "dd" dump of that image you will get that
expanded rootfs size. We normally recommend to run
"raw-disk-image-shrink-rootfs" on these type of images before
"from-raw-disk-image" command, which will ensure that the rootfs is
reduced in size.
To remedy the confusion here, simply run the
"raw-disk-image-shrink-rootfs" unconditionally when running
"from-raw-disk-image", this way it will not matter if the input image
has been "expanded" and the '--storage-total-size-mb' will always be
respected assuming that that the actual rootfs size does not overflow
the '--storage-total-size-mb' setting.
Because 'raw-disk-image-shrink-rootfs' is now a default, we also remove
the external command for this.
Changelog: shrink expanded rootfs when running "from_raw_disk_image"
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
Drew Moseley
Mirza Krak
Lluis Campos
Simon Guigui
Manuel Zedel
oleorhagen
Mario Kozjak
Simon Ensslen
Adam Podogrocki
Marek Belisko