To be able to use mender-convert as a git submodule its version needs
passing in as the docker environment does not have access to the parent project
to be able to traverse to get latest tag information
This is a fix for a previous regression
Changelog: Project can now be used as a git submodule again
Ticket: #MEN-6305
Signed-off-by: Dell Green <dell.green@ideaworks.co.uk>
Changelog: The mender-convert docker image does now contain the mender-convert application and does no longer need companion checkouts.
Changelog: All input files passed to docker-mender-convert must be located within the input directory as opposed to anywhere in the mender-convert checkout directory
Signed-off-by: Simon Ensslen <simon.ensslen@griesser.ch>
Previously the script would just exit 0, no matter the result of the conversion.
This simply exits with the exit code from the container, which is the exit code
from the conversion script.
Changelog: None
Signed-off-by: Ole Petter <ole.orhagen@northern.tech>
The suffix is random, so this will help the user to inspect the correct
log file.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
Previously there was a mix between two, and four spaces.
This commits unifies all scripts to use two-spaces for indentation.
Changelog: None
Signed-off-by: Ole Petter <ole.orhagen@northern.tech>
The reason for having a bind mount is unknown. In order to be able to
run this container fom inside another, the directory must be a volume.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
So that GitLab CI script (or any user, really) can customize the name of
the resulting Docker image.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@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>
To get rid of such errors/warnings as:
- mount: could not find any device /dev/loop#
- mount: ... WARNING: device write-protected, mounted read-only
access to host's kernel modules must be added.
Changelog: Title
Issues: MEN-2255
Signed-off-by: Adam Podogrocki <a.podogrocki@gmail.com>
This ensures we use same version of mender-convert inside
the container as the one used to launch the container.
It makes versioning and local development easier.
Changelog: Use local (checked out) version of mender-convert inside container
Signed-off-by: Eystein Måløy Stenberg <eystein.maloy.stenberg@northern.tech>
consistent and align with entry-point way of running mender-convert.
Changelog: None
Signed-off-by: Eystein Måløy Stenberg <eystein.maloy.stenberg@northern.tech>
It builds for both RPi3 and BBB, but there is a mount
warning for BBB, which may lead to it not working properly.
Changelog: Docker environment for running mender-convert
Signed-off-by: Eystein Måløy Stenberg <eystein.maloy.stenberg@northern.tech>
Dell Green
Fabio Tranchitella
Kristian Amlie
Simon Ensslen
Josef Holzmayr
Ole Petter
Lluis Campos
Drew Moseley
Mirza Krak
Adam Podogrocki
Max Bruckner
Eystein Måløy Stenberg