Building fresh IOT2000 SD-card image via a single command

This is a still just a preview, details of the commands are subject to change in the future.

If you like to get a fresh SD-card image for the IOT2000 using the development version at https://github.com/siemens/meta-iot2000, there is now a much simpler process available via Docker:

docker run --storage-opt size=50G -it kasproject/kas:latest sh -c "git clone https://github.com/siemens/meta-iot2000 -b jan/kas; kas build meta-iot2000/meta-iot2000-example/kas-iot2000-example-image.yml"

 Then you can retrieve the image by first finding out the container name that just ran:

docker ps -a

 Finally, copy out the image from that container:

docker cp -L <container>:build/build/tmp/deploy/images/iot2000/iot2000-example-image-iot2000.wic .

The build should take something between 40 minutes (high-end server), some 2 hours (decent 4-core machine with 8..16 GB and SSD), or it may have to run over night.

Looking forward to your feedback on this. I'm particularly interested in anyone having a Docker setup running under Windows (all my Windows machines are either virtual or historic): does the above work for you as well?

We will soon also describe a simple way to do this without Docker, directly on a Linux machine and merge those descriptions and configurations into meta-iot2000.

Hi jan-k, 

I changed way to build my customized image starting by Docker since I have a Windows machine.

I tried with the procedure descried on githHub but I'm not sure on how i have to compile the command. My share volume is C and I'm alredy logged in Docker, so i tried this:

docker run -v  /C --rm -t -i kasproject/kas:latest sh -c "git clone https://github.com/siemens/meta-iot2000 && kas build meta-iot2000/meta-iot2000-example/kas.yml" 

but it failed. (Next post for the log)

However, is possible to customize generated image with Docker after its building?

What's more, will be this image suitable for production purposes?

Thanks again for the help but, as you knew I believe, i'm new in this field.

Did you forget to post the log?

Regarding your second question: Yes, once you have built up a kas-based custom layer, you can also run the build with that layer inside docker. Just push the custom layer into the container (git clone or local mount), then use its kas.yml file to start the build.

Hi jan, 

Firstable sorry for the delay but I did some proves before to write to you again and i finally be able to build the image (with 11 Warnings, but it's normal, right?).

But now i'd like to "download" from the container to localhost but build/build/tmp... it not exist.

The first directory of the path it's builder. After having understood that i tried this command:

docker cp -L <containerID>:builder/build/tmp/deploy/images/iot2000/iot2000-exammple-image-iot2000.wic .

but after a few mitutes of research it displays that it can't find the file.

So i tried to download the whole directory iot2000 and for the file "iot2000-exammple-image-iot2000.wic" there is only a hyperlink (or it seems to be) and another that is called "iot2000-example-image-iot2000-20180117204053.rootfs.wic".

So, what is the right file that i have to use to customize the image? And how is the customization possible with docker? Because another kas process(according to bergmanu) will be overwrite bblayers.conf.

Thanks in advance for the help, and sorry again for the delay!

There is a typo in your path ("exammple"), maybe that is the problem.

The iot2000-example-image-iot2000.wic is a symbolic link to the actual image file which carries the build time in its name, thus is hard to reference in a generic document.

Regarding customization, please have a look at https://support.industry.siemens.com/tf/ww/en/posts/creating-custom-layer/182600/?page=0&pageSize=10. Once you have a custom layer with your own kas.yml, you pass that one into the docker container for building.

BTW, when developing customizations, I would recommend to map the build folder into the container (mount host directory as docker volume) rather than throwing it away after each build. You will have multiple runs and will soon appreciate not having to restart from the beginning each time. See README in latest meta-iot200 version.