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>
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>
It is a bit exessive to compile the mender client every time
the mender-convert tool is launched using docker-mender-convert.
Move the build to the Dockerfile so it is done during image
creation.
Changelog: Title
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
Ole Petter
Simon Ensslen
Kristian Amlie
Mirza Krak
Eystein Måløy Stenberg